Provider
SupabaseIncident detail
Unresponsive Projects
Resolved incidentMajor1 affected service
Timeline window
to
Get alerted the next time Supabase breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
Identified
We have identified why projects are becoming unresponsive and are implementing a mitigation.
Identified
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
Identified
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
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.
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.
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.
Resolved
This incident has been resolved.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.