Supabase incident

Project Actions Failing Across Multiple Regions

Major Resolved Upstream link ↗

Started

July 17, 2026 at 05:49 PM UTC

Duration

7h 51m

Resolved

July 18, 2026 at 01:41 AM UTC

Updates timeline

  1. Investigating

    Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.

  2. Investigating

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

  3. Investigating

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

  4. Investigating

    We are testing mitigation options to attempt to restore project action performance.

  5. Identified

    We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.

  6. Monitoring

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

  7. Resolved

    Project actions have been sustained at normal performance. This incident is resolved.

Get an email the next time Supabase goes down

Outage alerts for Supabase, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live Supabase status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader