Supabase Status · History · Incident #5644
RESOLVEDProject Actions Failing Across Multiple Regions
Major · Started Jul 17, 2026 · 5:49 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 #5644
RESOLVEDMajor · Started Jul 17, 2026 · 5:49 PM
Duration
7h 51m
Severity
Major
Detection lead
—
User reports
—
Summary
Project actions have been sustained at normal performance. This incident is resolved.
Started
Jul 17, 2026 · 5:49 PM
Resolved
Jul 18, 2026 · 1:41 AM
Duration
7h 51m
Severity
Major
Event timeline
Investigating
Jul 17 · 5:49 PM SupabaseCertain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Investigating
Jul 17 · 6:16 PM SupabaseProject actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Investigating
Jul 17 · 6:47 PM SupabaseWe have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Investigating
Jul 17 · 7:20 PM SupabaseWe are testing mitigation options to attempt to restore project action performance.
Identified
Jul 17 · 7:45 PM SupabaseWe have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
Monitoring
Jul 17 · 8:21 PM SupabaseThe mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
Resolved
Jul 18 · 1:41 AM SupabaseProject actions have been sustained at normal performance. This incident is resolved.
Pattern
Authentication issues for some projects
Jul 25, 2026 · 34m
View incident →Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade
Jul 23, 2026 · < 1m
View incident →Log Ingestion Problems
Jul 22, 2026 · 3h 40m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.