Incidentsby GlyphEndpoints in Americas regions returning 500 Internal server error
Jul 6, 14:45 UTCJul 6, 16:10 UTC
Duration
1h 25m
Impact
Major
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Management API
Final update
Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
Timeline
- Resolved · Jul 6, 16:10 UTC
Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
- Monitoring · Jul 6, 15:42 UTC
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.
- Identified · Jul 6, 15:15 UTC
We have identified the cause of the 500 errors and are implementing a fix.
- Investigating · Jul 6, 15:10 UTC
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
- Investigating · Jul 6, 14:47 UTC
The 500 errors are limited to us-east-1, we are actively exploring causes.
- Investigating · Jul 6, 14:45 UTC
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m