Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, last 194 days
Where, last 194 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.
2 down now · 19 places · 75 not pinned
Virginia (us-east-1): 17 incidents · Supabase, PlanetScale, Upstash, MongoDB Atlas, CockroachDB CloudAmsterdam (West Europe): 3 incidents · MongoDB AtlasCalifornia (us-west-1): 3 incidents · UpstashFrankfurt (eu-central-1): 3 incidents · UpstashIowa (us-central1): 3 incidents · CockroachDB Cloud, Upstash, PlanetScaleLondon (eu-west-2, europe-west2): 3 incidents · MongoDB Atlas, Upstash, PlanetScaleDublin (eu-west-1): 2 incidents · Supabase, UpstashMumbai (ap-south-1): 2 incidents · UpstashSão Paulo (southamerica-east1, sa-east-1): 2 incidents · CockroachDB Cloud, UpstashSydney (ap-southeast-2): 2 incidents · UpstashBrussels (europe-west1): 1 incident · UpstashIreland: 1 incident · SupabaseOhio (us-east-2): 1 incident · UpstashOregon (us-west-2): 1 incident · UpstashSeoul (ap-northeast-2): 1 incident · SupabaseSingapore (ap-southeast-1): 1 incident · UpstashTokyo (ap-northeast-1): 1 incident · UpstashBahrain (me-south-1): down now, 1 incident · MongoDB AtlasDubai (me-central-1): down now, 1 incident · MongoDB Atlas

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 · 84 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Wed, Oct 211 incident

16:27SEV 2Supabase · Intermittent connection errors via the connection pooler in us-east-1 · source0m

Tue, Oct 201 incident

19:38SEV 4PlanetScale · Gap in dashboard metrics for AWS us-east-1 · source1h 08m

Fri, Oct 91 incident

22:53SEV 2PlanetScale · AWS us-east-1 connectivity failures · source26m

Tue, Sep 291 incident

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

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

Wed, Sep 91 incident

13:00SEV 2Upstash · Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1) · source0m

Fri, Aug 281 incident

22:56SEV 2Upstash · Message Persistence Issue — QStash us-east-1 · source0m

Sat, Jul 181 incident

20:32SEV 2PlanetScale · Connectivity issues in us-east-1 · source33m

Thu, Jul 161 incident

08:35SEV 2Upstash · QStash us-east-1 - URL Publish Errors · source0m

Thu, Jun 251 incident

15:23SEV 2Upstash · Upstash Redis Partial Service DisruptionRedis Global - N. Virginia, USA (us-east-1), Redis Global - N. California, USA (us-west-1), Redis Global - Frankfurt, Germany (eu-central-1) · source1h 12m

Fri, May 291 incident

20:18SEV 2Upstash · Intermittent slowness in Vector US-EAST-1 regionAWS - US-EAST-1, Vector - AWS - US-EAST-1 · source11h 33m

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

Thu, May 141 incident

15:47SEV 2Upstash · Upstash Redis – intermittent connection issues in some regionsRedis Global - N. Virginia, USA (us-east-1), Redis Global - N. California, USA (us-west-1), Redis Global - Sydney, Australia (ap-southeast-2) +1 · source1h 44m

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