← Back to Supabase History
major✓ Resolved

Endpoints in Americas regions returning 500 Internal server error

SupabaseMon, Jul 6, 2026, 02:45 PM
Status
resolved
Duration
1h 29m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedMon, Jul 6, 2026, 04:15 PM
This incident has been resolved.
monitoringMon, Jul 6, 2026, 03:42 PM
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.
identifiedMon, Jul 6, 2026, 03:15 PM
We have identified the cause of the 500 errors and are implementing a fix.
investigatingMon, Jul 6, 2026, 03:10 PM
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
investigatingMon, Jul 6, 2026, 02:47 PM
The 500 errors are limited to us-east-1, we are actively exploring causes.
investigatingMon, Jul 6, 2026, 02:45 PM
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.

📊 TECHNICAL DETAILS

Internal ID
0779b0df-8503-4bca-9e3c-aef6a79752b3
External ID
mkt5vw3qxh08
🕐 Started
Mon, Jul 6, 2026, 02:45 PM
🔄 Last Updated
Mon, Jul 6, 2026, 04:15 PM
✓ Resolved
Mon, Jul 6, 2026, 04:15 PM
MAJOR
Impact Level
1h 29m
Total Duration
5
Status Updates
Affected Components
Management API
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed