Supabase incident
Endpoints in Americas regions returning 500 Internal server error
Resolved after 1 hour 25 minutes, affecting Management API, on July 6, 2026.
Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
Affected components
Update timeline
- investigating Jul 06, 2026, 02:45 PM UTC
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
- investigating Jul 06, 2026, 02:47 PM UTC
The 500 errors are limited to us-east-1, we are actively exploring causes.
- investigating Jul 06, 2026, 03:10 PM UTC
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
- identified Jul 06, 2026, 03:15 PM UTC
We have identified the cause of the 500 errors and are implementing a fix.
- monitoring Jul 06, 2026, 03:42 PM UTC
The fix has been applied and there are improvements to the error rates. We are continued to work on ensuring the underlying issue does not recur.
- resolved Jul 06, 2026, 04:10 PM UTC
Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services