Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 374 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.
4 places · 5 not pinned
Virginia (us-east-1): 2 incidents · SupabaseDublin (eu-west-1): 1 incident · SupabaseIreland: 1 incident · SupabaseSeoul (ap-northeast-2): 1 incident · Supabase
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 73 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

21:59SEV 2Supabase · Projects stuck in restarting state · source7h 41m

Mon, Oct 121 incident

22:59SEV 2Supabase · Realtime latency · source45h 26m

Tue, Sep 291 incident

16:26SEV 2Supabase · Intermittent latency in Eastern US · source6d 19h

Thu, Sep 241 incident

15:36SEV 2Supabase · Project Lifecycle Issues in eu-west-1 · source2h 02m

Wed, Sep 231 incident

09:31SEV 2Supabase · Storage search failing for restored projects · source24h 30m

Tue, Sep 221 incident

11:09SEV 2Supabase · Supavisor connection disruptions in EU West 1 (Ireland) · source1h 11m

Wed, Sep 162 incidents

17:54SEV 2Supabase · 2 incidents5h 45m
17:54SEV 2Supabase · Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2 · source2h 42m
09:24SEV 2Supabase · Edge Function Latency · source3h 03m