← Back to Supabase History
major✓ Resolved

Unresponsive Projects

SupabaseThu, Sep 10, 2026, 03:26 PM
Status
resolved
Duration
1d 3h
Updates
7
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, Sep 11, 2026, 07:10 PM
This incident has been resolved.
monitoringFri, Sep 11, 2026, 06:19 AM
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.
monitoringFri, Sep 11, 2026, 03:44 AM
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.
identifiedThu, Sep 10, 2026, 07:41 PM
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.
identifiedThu, Sep 10, 2026, 05:59 PM
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
identifiedThu, Sep 10, 2026, 05:13 PM
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
identifiedThu, Sep 10, 2026, 03:46 PM
We have identified why projects are becoming unresponsive and are implementing a mitigation.
investigatingThu, Sep 10, 2026, 03:26 PM
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

📊 TECHNICAL DETAILS

Internal ID
ad0270fa-ba79-4fde-85a3-5ad6d67bd327
External ID
4mkcsnlf6p5x
🕐 Started
Thu, Sep 10, 2026, 03:26 PM
🔄 Last Updated
Fri, Sep 11, 2026, 07:10 PM
✓ Resolved
Fri, Sep 11, 2026, 07:10 PM
MAJOR
Impact Level
1d 3h
Total Duration
7
Status Updates
Affected Components
Database
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed