Supabase outage — August 24, 2026
Issues affecting automatic disk resizing
Supabase’s Multiple services was disrupted for 4h 59m on August 24, 2026. 503Radar’s sensors raised the first signal at 10:09 UTC, 3h 43m before the official status page acknowledged impact.
Key facts
| Detected | August 24, 2026 · 10:09 UTC |
| Confirmed | 13:53 UTC · lead time 3h 43m |
| Resolved | 15:09 UTC |
| Duration | 4h 59m |
| Service | Multiple services |
| Official record | https://stspg.io/fdx6ybdwplv5 |
Timeline
- 10:09Z
Detected · Signal
1 crowd signal for Multiple services on SUPABASE crossed the signal threshold. - 13:53Z
Confirmed · Official
An official SUPABASE status-page notice corroborated the event — 3h 43m after detection. - 15:09Z
Resolved
Signal volume fell back below the threshold; the event was closed.
How this was detected
1 independent evidence class for Multiple services on SUPABASE. 1 crowd report across bluesky (single platform — not corroborating), z=-0.4σ vs the cell baseline. Official notice confirms it, 3h 43m after the crowd.