Supabase Status · History · Incident #2142
RESOLVEDNetwork connectivity in us-east-1-az4
Major · Started May 8, 2026 · 12:50 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Supabase Status · History · Incident #2142
RESOLVEDMajor · Started May 8, 2026 · 12:50 AM
Duration
1d 3h 59m
Severity
Major
Detection lead
—
User reports
—
Summary
Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.
Started
May 8, 2026 · 12:50 AM
Resolved
May 9, 2026 · 4:49 AM
Duration
1d 3h 59m
Severity
Major
Event timeline
Investigating
May 8 · 12:50 AM SupabaseIncreased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1
Identified
May 8 · 1:06 AM SupabaseWe 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
May 8 · 2:05 AM SupabaseWe are waiting on a resolution from our upstream provider. We will provide an update in an hour.
Identified
May 8 · 2:30 AM SupabaseWe have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
Identified
May 8 · 3:11 AM SupabaseWe'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
May 8 · 4:21 AM SupabaseWe are continuing to work on a fix for this issue.
Identified
May 8 · 5:30 AM SupabaseWe are continuing to work on a fix for this issue.
Identified
May 8 · 5:31 AM SupabaseWe'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
May 8 · 6:44 AM SupabaseAffected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
Identified
May 8 · 7:59 AM SupabaseAffected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
Identified
May 8 · 10:52 AM SupabaseAffected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
Identified
May 8 · 12:09 PM SupabaseOur 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
May 8 · 4:34 PM SupabaseOur 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
May 9 · 1:32 AM SupabaseOur 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
May 9 · 4:10 AM SupabaseOur 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
May 9 · 4:34 AM SupabaseOur 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
May 9 · 4:49 AM SupabaseRecovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT