Supabase Status · History · Incident #4232
RESOLVEDErrors impacting pause, restore, and backup operations in us-east-2 (Ohio)
Critical · Started Jun 2, 2026 · 1:36 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 #4232
RESOLVEDCritical · Started Jun 2, 2026 · 1:36 PM
Duration
1h 5m
Severity
Critical
Detection lead
—
User reports
—
Summary
All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.
Started
Jun 2, 2026 · 1:36 PM
Resolved
Jun 2, 2026 · 2:41 PM
Duration
1h 5m
Severity
Critical
Event timeline
Investigating
Jun 2 · 1:36 PM SupabaseWe are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.
Identified
Jun 2 · 2:05 PM SupabaseWe have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.
Monitoring
Jun 2 · 2:12 PM SupabaseThe redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.
Resolved
Jun 2 · 2:41 PM SupabaseAll operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.
Pattern
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