Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, Sep 15–29, 2026Clean: 36 providers
Where, Sep 15–29, 2026Places named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
7 down now · 14 places · 64 not pinned
Virginia (us-east-1): 3 incidents · Upstash, AWS, SupabaseOregon: 2 incidents · RenderDublin (eu-west-1): 1 incident · SupabaseIreland: 1 incident · SupabaseSão Paulo (southamerica-east1): 1 incident · CockroachDB CloudSeoul (ap-northeast-2): 1 incident · SupabaseSingapore (Southeast Asia): 1 incident · RailwayBahrain (me-south-1): down now, 2 incidents · MongoDB Atlas, AWSDubai (me-central-1): down now, 2 incidents · MongoDB Atlas, AWSUnited States: down now, 2 incidents · TwilioBrazil: down now, 1 incident · TwilioIsrael: down now, 1 incident · TwilioRomania: down now, 1 incident · TwilioUnited Kingdom: down now, 1 incident · Twilio

Region only: Europe 3

Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 70 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Tue, Sep 291 incident

15:36SEV 2Upstash · Brief connection proxy degradation in us-east-1 · source0m

Mon, Sep 211 incident

23:26SEV 2AWS · [RESOLVED] Increased Error Ratesus-east-1 · source58m

Wed, Sep 161 incident

17:54SEV 2Supabase · Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2 · source2h 42m