Affected components
Update timeline
- 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.
- 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
- 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
- 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.
- 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.
Looking to track Supabase downtime and outages?
Pingoru polls Supabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Supabase reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Supabase alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required