Supabase incident
Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1
Supabase experienced a major incident on April 25, 2026 affecting ap-northeast-1 and us-east-2, lasting 1h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 25, 2026, 04:16 AM UTC
We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information.
- identified Apr 25, 2026, 04:26 AM UTC
US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions.
- identified Apr 25, 2026, 04:38 AM UTC
Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event.
- monitoring Apr 25, 2026, 05:14 AM UTC
Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.
- resolved Apr 25, 2026, 05:47 AM UTC
This issue has now been resolved and projects have returned to normal.