Supabase is degraded.
0 days since last incident
Active incident
Predicted resolution
n=46~124m (p25 54m – p75 235m)
Similar minor incidents on Supabase have resolved in ~124 min, median of 46 in the past 180 days · 26171m elapsed so far.
71.931% of the last 30 days with no impact declared by Supabase. That is their disclosure record, not a measurement of availability. Full history on the Supabase reliability scorecard.
Aug 31, 16:28 UTC · resolved in 2h 41m · Resolved
Aug 27, 17:20 UTC · resolved in 3d 22h · Resolved
Aug 26, 19:49 UTC · resolved in 22h 35m · Resolved
Official status page: https://status.supabase.com (opens in new tab)
Aug 24, 13:52 UTC · resolved in 2h 2m · Resolved
Aug 19, 15:52 UTC · resolved in 2m · Resolved
Aug 17, 01:47 UTC · resolved in 7m · Resolved
Aug 14, 09:31 UTC · resolved in 9m · Resolved
Aug 14, 09:31 UTC · resolved in 1h 19m · Resolved
Aug 14, 02:23 UTC · resolved in 12m · Resolved
Aug 14, 02:23 UTC · in progress · Identified
Aug 3, 15:28 UTC · resolved in 2d 2h · Resolved