Supabase incident

Unresponsive Projects

Major Resolved Upstream link ↗

Started

September 10, 2026 at 03:26 PM UTC

Duration

1d 3h

Resolved

September 11, 2026 at 07:06 PM UTC

Updates timeline

  1. Investigating

    We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

  2. Identified

    We have identified why projects are becoming unresponsive and are implementing a mitigation.

  3. Identified

    A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.

  4. Identified

    Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.

  5. Identified

    We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.

  6. Monitoring

    We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.

  7. Monitoring

    We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.

  8. Resolved

    This incident has been 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