8 live incidents
Provider status, from real traffic.
Detected from production requests across every provider we route to, not from status pages. An incident is a capacity-error spike (over 10% of requests failing) or a latency spike (p50 at 2.5x the provider's own 24 hour baseline). Our latency router shifts traffic away from degraded providers within minutes; requests using it ride through most of these without noticing.
30providers watched
9clean for 24 hours
100incidents in 24 hours
8open right now
01The wall
Provider health, last 24 hours
Every provider we route to, in 30 minute buckets, weighted across the endpoints we call. Teal is a window where the traffic went through. Anything else is a window the record below has a row for.
02The record
Every incident, last 24 hours
One row per degradation we measured, named and timed. Sort any column to ask a different question: who lost the most requests, whose spike ran longest, whose day is not over.
Snapshot 04:14:40 UTC · refreshes every 60s · fetch it yourself: GET /public/v1/incidents
