Supabase incident

Database issues in us-east-2

Minor Resolved View vendor source →

Supabase experienced a minor incident on March 3, 2026 affecting Database, lasting 4h 20m. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2026, 02:10 AM UTC
Resolved
Mar 03, 2026, 06:31 AM UTC
Duration
4h 20m
Detected by Pingoru
Mar 03, 2026, 02:10 AM UTC

Affected components

Database

Update timeline

  1. investigating Mar 03, 2026, 02:10 AM UTC

    We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate.

  2. identified Mar 03, 2026, 02:41 AM UTC

    We’ve identified that this affects only a subset of projects in us-east-2. We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general

  3. identified Mar 03, 2026, 03:14 AM UTC

    We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general

  4. monitoring Mar 03, 2026, 04:08 AM UTC

    We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment.

  5. resolved Mar 03, 2026, 06:31 AM UTC

    Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners.