Supabase incident

Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)

Critical Resolved View vendor source →

Supabase experienced a critical incident on June 2, 2026 affecting Management API, lasting 1h 5m. The incident has been resolved; the full update timeline is below.

Started
Jun 02, 2026, 01:36 PM UTC
Resolved
Jun 02, 2026, 02:41 PM UTC
Duration
1h 5m
Detected by Pingoru
Jun 02, 2026, 01:36 PM UTC

Affected components

Management API

Update timeline

  1. investigating Jun 02, 2026, 01:36 PM UTC

    We 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.

  2. identified Jun 02, 2026, 02:05 PM UTC

    We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.

  3. monitoring Jun 02, 2026, 02:12 PM UTC

    The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.

  4. resolved Jun 02, 2026, 02:41 PM UTC

    All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.