Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, Apr 29 – May 13, 2026Clean: Supabase, PlanetScale
Where, Apr 29 – May 13, 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.
2 down now · 4 places · 5 not pinned
Virginia (us-east-1): 4 incidents · Upstash, MongoDB Atlas, CockroachDB CloudAmsterdam (West Europe): 1 incident · MongoDB AtlasBahrain (me-south-1): down now, 1 incident · MongoDB AtlasDubai (me-central-1): down now, 1 incident · MongoDB Atlas
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 84 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Fri, May 83 incidents

09:46SEV 2Upstash · QStash US Region Service DisruptionQStash - US-EAST-1 · postmortem · source22m
02:24SEV 2MongoDB Atlas · AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMongoDB Cloud · source36h 00m
02:13SEV 2CockroachDB Cloud · Degraded performance in one AWS us-east-1 availability zoneCockroachDB Advanced · source19h 40m

Tue, May 51 incident

14:24SEV 2Upstash · QStash US Region: Schedule DegradationQStash - US-EAST-1 · postmortem · source17h 41m