Live component health and 90-day availability. This page is served from every ingest
host and does not depend on the control plane.
All systems operational, with elevated probe latency in sa-east.
Last updated 12 Oct 2026, 11:58 UTC.
Component
Status
90d
Ingest — eu-central
operational
100.00%
Ingest — eu-west
operational
100.00%
Ingest — uk-south
operational
99.99%
Ingest — us-east
operational
100.00%
Ingest — us-west
operational
99.98%
Ingest — ap-south
operational
99.97%
Ingest — ap-southeast
operational
100.00%
Control plane
operational
100.00%
HTTP API
operational
99.99%
Alert delivery
operational
100.00%
Probe mesh — sa-east
elevated latency
98.71%
Bulk export
operational
99.95%
Incident history
Elevated probe latency in sa-east
A transit provider in São Paulo rerouted traffic through Miami, adding roughly 90 ms to
checks originating from sa-east. No checks failed and no results were lost;
duration histograms from that vantage point are skewed for the window and are annotated in the
API response.
Delayed alert delivery
A queue consumer in the alerting tier stopped acknowledging after a deploy, delaying
notifications by up to 14 minutes for about 6% of workspaces. Check execution and ingest were
unaffected. We have added a liveness probe on consumer lag and a rollback gate on it.
ap-south ingest rejected new connections
Certificate rotation on the Mumbai ingest host completed out of order, so agents reconnecting
during a 22-minute window were rejected with a TLS alert. Agents spooled locally and replayed on
reconnect; no samples were lost. Rotation is now gated on a successful handshake from an
out-of-band canary.
Partial bulk export failures
Export jobs covering more than 90 days failed with a timeout after a storage migration. Retried
jobs succeeded. Export now streams in 30-day chunks.
Subscribe
Status changes are published as an Atom feed and as webhooks. Add
https://status.pingform.org/feed.atom to your reader, or configure a webhook in the
console under Workspace → Notifications.