Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, May 13–27, 2026
A+Upstash10m
Clean: 38 providers
Where, May 13–27, 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 · 16 places · 10 not pinned
London (eu-west-2): 2 incidents · Upstash, PlanetScaleBrussels (europe-west1): 1 incident · UpstashCalifornia (us-west-1): 1 incident · UpstashDublin (eu-west-1): 1 incident · UpstashFrankfurt (eu-central-1): 1 incident · UpstashIowa (us-central1): 1 incident · UpstashMumbai (ap-south-1): 1 incident · UpstashOhio (us-east-2): 1 incident · UpstashOregon (us-west-2): 1 incident · UpstashSão Paulo (sa-east-1): 1 incident · UpstashSingapore (ap-southeast-1): 1 incident · UpstashSydney (ap-southeast-2): 1 incident · UpstashTokyo (ap-northeast-1): 1 incident · UpstashVirginia (us-east-1): 1 incident · UpstashBahrain (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 · 88 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Fri, May 221 incident

23:27SEV 3Upstash · New Database Creation Failing Due to Upstream Provider IssueRedis Global - N. Virginia, USA (us-east-1), Redis Global - N. California, USA (us-west-1), Redis Global - Oregon, USA (us-west-2) +13 · source32m