Supabase outage on November 12, 2026: Storage request degradation in eu-west-1
Supabase reported an incident affecting Supabase for 8 minutes on 12 November 2026, from 14:48 to 14:56 UTC.
Resolved
Official incident reported by Supabase
- Started
- 14:48
- 12 Nov 2026 UTC
- Resolved
- 14:56
- 12 Nov 2026 UTC
- Duration
- 8m
- 8 minutes
- Impact
- Minor
- as rated by Supabase
- Updates
- 2
- posted by Supabase
Timeline
All times UTC.
Official incident from Supabase
Storage request degradation in eu-west-1
-
Official
Monitoring
Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.
-
Official
Resolved
We have mitigated the issue with the Storage service and we have not observed any further issues during our monitoring period. We consider this incident to be resolved.
"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.
Does your product depend on Supabase?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.