Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, Jun 24 – Jul 8, 2026
BAWS151m
Clean: 38 providers
Where, Jun 24 – Jul 8, 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.
6 down now · 10 places · 28 not pinned
Virginia (us-east-1, East US): 3 incidents · AWS, Vercel, UpstashCalifornia (us-west-1): 1 incident · UpstashFrankfurt (eu-central-1): 1 incident · UpstashStockholm (eu-north-1): 1 incident · AWSBahrain (me-south-1): down now, 2 incidents · MongoDB Atlas, AWSBrazil: down now, 2 incidents · TwilioDubai (me-central-1): down now, 2 incidents · MongoDB Atlas, AWSUnited States: down now, 2 incidents · TwilioArgentina: down now, 1 incident · TwilioRomania: down now, 1 incident · Twilio

Region only: North America 1

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

Tue, Jun 301 incident

21:02SEV 2AWS · [RESOLVED] Increased Error Rates and Latencieseu-north-1 · source51m