Supabase outage — July 17, 2026
Project Actions Failing Across Multiple Regions
Supabase’s Multiple services was disrupted for 2h 56m on July 17, 2026. 503Radar’s sensors raised the first signal at 15:28 UTC, 2h 24m before the official status page acknowledged impact.
Key facts
| Detected | July 17, 2026 · 15:28 UTC |
| Confirmed | 17:53 UTC · lead time 2h 24m |
| Resolved | 18:24 UTC |
| Duration | 2h 56m |
| Service | Multiple services |
| Official record | https://stspg.io/xf7wf1421m7x |
Timeline
- 15:28Z
Detected · Signal
1 crowd signal for Multiple services on SUPABASE crossed the signal threshold. - 17:53Z
Confirmed · Official
An official SUPABASE status-page notice corroborated the event — 2h 24m after detection. - 18:24Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“Supabase RLS Policies Silently Failing: How to Debug Them RLS failures don't throw errors — they return empty results. Here is exactly how to find and fix the m”bluesky_jetstream · 15:16 UTC
How this was detected
1 independent evidence class for Multiple services on SUPABASE. 1 crowd report across bluesky (single platform — not corroborating), z=-0.1σ vs the cell baseline. Official notice confirms it, 2h 24m after the crowd.