Supabase experienced a major incident on February 12, 2026, lasting 4h 21m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Feb 12, 2026, 09:32 PM UTC
We have identified increasing 500 errors in some US regions and are actively investigating the cause.
- investigating Feb 12, 2026, 10:37 PM UTC
The issue identified it as a problem in US-West with some impact in US-East and the impact seems to be primarily on reads rather than writes.
- investigating Feb 12, 2026, 10:57 PM UTC
We continue to see increased levels of 500 errors across US-West and US-East regions. Our engineering team is investigating the issue.
- investigating Feb 12, 2026, 11:58 PM UTC
We are still investigating the root cause for this incident. us-east-2 region isn’t receiving any network traffic at this point. We are also seeing some API request errors in other US regions, but not as high as us-east-2.
- identified Feb 13, 2026, 01:04 AM UTC
We identified a potential internal networking configuration that may have caused the incident. We have since reverted that change and it appears services are recovering.
- monitoring Feb 13, 2026, 01:26 AM UTC
The revert of the change helped and most of the metrics are back to the pre incident levels. We are requeuing failed jobs and monitoring to make sure the issue doesn’t come back.
- resolved Feb 13, 2026, 01:53 AM UTC
Service has been fully restored. All impacted jobs have been requeued and are currently processing normally. We will be publishing a public post-mortem with additional details about this incident.
- postmortem Feb 14, 2026, 03:26 AM UTC
We’ve published a [post-mortem on our blog](https://supabase.com/blog/supabase-incident-on-february-12-2026).