Supabase incident history

Right now: minor open (1 open), by Supabase's own status page, mirrored every five minutes.

50
incidents kept since 30 Jun 2026
20
in the last 30 days
2h 2m
median time to resolve, once posted
29%
resolved within an hour

How far back this goes: Supabase's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 88 days so far and grows from here. Impact labels (17 major or critical) are Supabase's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares Supabase as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind Supabase are watched.

Which parts of Supabase the incidents touched

Database
8
Management API
6
Dashboard
6
us-east-2
4
eu-west-1
4
eu-west-3
3

Every incident we hold, newest first

23 Sept 2026
minor
1h 42m
16 Sept 2026
minor
3h 2m
16 Sept 2026
minor
2h 16m
10 Sept 2026
major
1d 3h
31 Aug 2026
major
2h 38m
21 Aug 2026
none
1h 48m
3 Aug 2026
minor
2d 2h
31 Jul 2026
minor
58m 23s
30 Jul 2026
minor
52m 37s
28 Jul 2026
minor
42m 41s
28 Jul 2026
minor
6m 30s
22 Jul 2026
minor
3h 40m
9 Jul 2026
minor
4h 13m

Source: Supabase's public status page at status.supabase.com, mirrored every five minutes. Data as JSON: /upstream/supabase/incidents.json. CC BY 4.0.

If your site depends on Supabase, Repose holds the page when the cause is upstream. How the hold decision works →