← Back to Supabase History
minor✓ Resolved

Database issues in us-east-2

Supabase•Tue, Mar 3, 2026, 02:10 AM
Status
resolved
Duration
4h 24m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedTue, Mar 3, 2026, 06:35 AM
This incident has been resolved.
monitoringTue, Mar 3, 2026, 04:08 AM
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.
identifiedTue, Mar 3, 2026, 03:14 AM
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
identifiedTue, Mar 3, 2026, 02:41 AM
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
investigatingTue, Mar 3, 2026, 02:10 AM
We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate.

📊 TECHNICAL DETAILS

Internal ID
2fcdc221-fa8e-43cf-8896-a57620ed0dc3
External ID
ktlmc2pqh6k7
🕐 Started
Tue, Mar 3, 2026, 02:10 AM
🔄 Last Updated
Tue, Mar 3, 2026, 06:35 AM
✓ Resolved
Tue, Mar 3, 2026, 06:35 AM
MINOR
Impact Level
4h 24m
Total Duration
4
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