Operational status
System status
Live healthchecks · refreshed every 30s
Probing endpoints…
Initial probe in flight — first results land in a moment.
01 · Section
Components
Live probes against the production endpoints. Latency window is the last 60 samples (~30 minutes).
Live probes against the production endpoints. Latency window is the last 60 samples (~30 minutes).
02 · Section
90-day history
Per-component daily roll-up. Cells start filling from your first visit; older cells appear empty until back-filled by a server-side store.
Per-component daily roll-up. Cells start filling from your first visit; older cells appear empty until back-filled by a server-side store.
03 · Section
Incident log
No customer-impacting incidents reported
Customer-impacting incidents are emailed to tenant owners and posted here with a timeline + post-mortem. Internal degradations that don't affect customers are tracked but not surfaced to this page.
Last incident
—
Open incidents
0
Mean time to resolve
—
04 · Section
How this page works
So you can trust what you're reading.
So you can trust what you're reading.
What we probe
Each component row probes a real production endpoint from your browser. The health check passes only when the application is fully booted, and the readiness check passes only when the database and cache are reachable. A sample is marked ‘slow’ above 2,000 ms and ‘down’ on any error response or network failure.
Where the history lives
The 90-day uptime grid is computed in your browser from samples we persist to localStorage as you visit. A central store will replace this once the platform has aggregate traffic to justify it; until then, cells before your first visit appear empty rather than fake-green.