Supabase Status · History · Incident #81
RESOLVEDSome projects unavailable across multiple regions
Major · Started Apr 27, 2026 · 12:39 PM
$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 #81
RESOLVEDMajor · Started Apr 27, 2026 · 12:39 PM
Duration
6h 24m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Apr 27, 2026 · 12:39 PM
Resolved
Apr 27, 2026 · 7:04 PM
Duration
6h 24m
Severity
Major
Event timeline
Identified
Apr 27 · 12:39 PM SupabaseWe are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects
Identified
Apr 27 · 1:31 PM SupabaseThe team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.
Identified
Apr 27 · 1:38 PM SupabaseWe have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.
Identified
Apr 27 · 3:00 PM SupabaseThe team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.
Identified
Apr 27 · 4:22 PM SupabaseThe team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed.
Monitoring
Apr 27 · 6:34 PM SupabaseWe believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue.
Resolved
Apr 27 · 7:04 PM SupabaseThis incident has been resolved.
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