Supabase outage on July 6, 2026
Supabase users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Major severity and lasted ongoing. The stored report window does not show a preserved user-report spike.
Jul 6, 15:10 UTC Update - The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains. Jul 6, 14:47 UTC Update - The 500 errors are limited to us-east-1, we are actively exploring causes. Jul 6, 14:45 UTC Investigating - Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
Deterministic readout · awaiting AI summary pass
Incident detected
Major confidence crossed the incident threshold for Supabase: endpoints in Americas regions returning 500 Internal server error.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
80.00The incident reached 80.00 peak confidence across 37 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
OpenThis incident is still open in the incident record and should be treated as ongoing until resolved.