Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 284 daysPlaces 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.
14 places · 9 not pinned
Virginia (us-east-1): 11 incidents · UpstashCalifornia (us-west-1): 3 incidents · UpstashFrankfurt (eu-central-1): 3 incidents · UpstashMumbai (ap-south-1): 2 incidents · UpstashSydney (ap-southeast-2): 2 incidents · UpstashTokyo (ap-northeast-1): 2 incidents · UpstashBrussels (europe-west1): 1 incident · UpstashDublin (eu-west-1): 1 incident · UpstashIowa (us-central1): 1 incident · UpstashLondon (eu-west-2): 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 · Upstash

Region only: Europe 1

Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 90 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

Fri, Mar 61 incident

13:50SEV 2Upstash · Region ap-northeast-1 outage on Upstash GlobalRedis Global - Tokyo, Japan (ap-northeast-1) · postmortem · source1h 00m