AppStructStatus

Subscribe appstruct.ai

Incident history

Incidents and maintenance from the last 90 days, newest first.

No incidents in the last 90 days.

How this page works

A monitor in Frankfurt (fra1) checks 12 services every 5 min, with one request each to a lightweight health endpoint. A failed check gets one retry 2 seconds later before it counts, so a dropped packet doesn’t paint the page red.
Opening this page never touches AppStruct’s servers. It is a cached snapshot that refreshes after each round of checks. If scheduled checks ever stop, a visit can start one overdue round — still never more often than the interval above.
A service counts as degraded when it takes longer than 3 seconds to respond, and as down when it fails, times out after 10 seconds or returns something unexpected. Two failed rounds in a row open an incident automatically; slowness needs three.
Uptime is the share of successful checks. Checks during announced maintenance are left out. Days are counted in UTC, and the bars show only what was actually measured — days before monitoring started stay grey.
Third-party statuses come straight from each provider’s public status page.

Atom feed JSON API appstruct.ai support@appstruct.cloud

© 2026 AppStruct