Platform status
What is running, and what is not.
Each component reports its own reading or says it has none. A component with no reading is shown as not connected, never as healthy by default.
Component health
Not connected
The status feed is not connected. The public status endpoint is pending, so no component on this page has a live reading, and none is shown as healthy by default.
Official-source feed · no endpoint is configured for this environment
Verification API
no reading · status feed not connectedCapture ingest
no reading · status feed not connectedOfficial-source feed
no endpoint is configured for this environmentMonitors
no reading · status feed not connectedService health check
RespondingMeasured from this page when it loaded: the service answered its health check. This is the only reading this page has.
Capture ingest
no reading publishedOfficial-source feed
no reading publishedMonitors
no reading publishedService health check
Not healthyMeasured from this page when it loaded: the service answered its health check and reported that it is not healthy. No further detail is published here.
Capture ingest
no reading publishedOfficial-source feed
no reading publishedMonitors
no reading publishedPlatform record
- Migration head
- reported by the status feed · pending
- Last monitor run
- reported by the status feed · pending
- Count-window posture
-
none active · no engagement is in a counting window; nothing on this page is a live count
- Seal state
- no reading published
Incident history
Incident log · not published
No incident history is published yet.
This page reads one health check. It has no incident log to show, so it shows none: no past incident is listed here, and the absence of a list is not a statement that nothing ever happened.
Incidents are opened by a named role, not by an alerting rule, and stay on this page after they close.