Supabase Status · History · Incident #3918
RESOLVEDBranch creation degradation
Minor · Started May 21, 2026 · 4:46 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 #3918
RESOLVEDMinor · Started May 21, 2026 · 4:46 PM
Duration
2h 39m
Severity
Minor
Detection lead
—
User reports
—
Summary
Branch creation continues to be stable.
Started
May 21, 2026 · 4:46 PM
Resolved
May 21, 2026 · 7:26 PM
Duration
2h 39m
Severity
Minor
Event timeline
Investigating
May 21 · 4:46 PM SupabaseWe are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.
Investigating
May 21 · 5:45 PM SupabaseWe continue investigating different possible underlying causes and will provide updates as progress is made.
Monitoring
May 21 · 6:54 PM SupabaseBranch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.
Resolved
May 21 · 7:26 PM SupabaseBranch creation continues to be stable.
Pattern
Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)
Jun 2, 2026 · 1h 5m
View incident →Login issues for SSO and Email accounts on Supabase Dashboard
May 21, 2026 · 2h 20m
View incident →Network restrictions preventing read replica communication
May 20, 2026 · 7h 40m
View 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