Supabase · incident

Unresponsive Projects

Provider lifecycle: monitoring

Get one resolution alert

Enter an email and we’ll send a confirmation link. We use it only for this incident and delete it after the alert.

Partial outage
Provider incident confirmed

Supabase Status has not marked this as resolved. The latest official update is shown first below.

Official timeline

Provider updates

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

    Affected: Database

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

    Affected: Database

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

    Affected: Database

  4. identified

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

    Affected: Database

  5. identified

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

    Affected: Database

  6. identified

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

    Affected: Database

  7. investigating

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

    Affected: Database