Supabase incident
Network connectivity in us-east-1-az4
Started
May 8, 2026 at 12:50 AM UTC
Duration
1d 3h
Resolved
May 9, 2026 at 04:49 AM UTC
Updates timeline
- Investigating
Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1
- Identified
We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone.
- Identified
We are waiting on a resolution from our upstream provider. We will provide an update in an hour.
- Identified
We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
- Identified
We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider.
- Identified
We are continuing to work on a fix for this issue.
- Identified
We are continuing to work on a fix for this issue.
- Identified
We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects.
- Identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
- Identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
- Identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
- Identified
Our team is actively working to bring impacted projects back online as quickly and safely as possible. While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider. We appreciate your patience and will continue to share updates as more information becomes available.
- Identified
Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.
- Identified
Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.
- Identified
Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered. Our team is currently working through the remaining projects that did not automatically self-heal during recovery and is actively restoring them manually where needed. We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region. We are continuing to monitor platform stability closely and will provide additional updates as recovery progresses.
- Monitoring
Our infrastructure provider has resolved the underlying incident, and impacted services have recovered. We have completed recovery efforts for affected projects, re-enabled project creation, pausing, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability.
- Resolved
Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.
Live Supabase status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader