Provider
SupabaseIncident detail
Endpoints in Americas regions returning 500 Internal server error
Resolved incidentMajor
Timeline window
to
Outage alerts
Get alerted the next time Supabase breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
Investigating
The 500 errors are limited to us-east-1, we are actively exploring causes.
Investigating
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
Identified
We have identified the cause of the 500 errors and are implementing a fix.
Monitoring
The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.
Resolved
Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
Resolved
OutageDeck marked this incident resolved after it no longer appeared in the upstream active incident summary at 2026-07-06T16:15:01.704Z.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.