Supabase outage on October 22, 2026: Log Drain Issues
Supabase reported an incident affecting Supabase for 47 minutes on 22 October 2026, from 18:03 to 18:50 UTC.
Resolved
Official incident reported by Supabase
- Started
- 18:03
- 22 Oct 2026 UTC
- Resolved
- 18:50
- 22 Oct 2026 UTC
- Duration
- 47m
- 47 minutes
- Impact
- Minor
- as rated by Supabase
- Updates
- 3
- posted by Supabase
Timeline
All times UTC.
Official incident from Supabase
Log Drain Issues
-
Official
Investigating
Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
-
Official
Monitoring
The rollback has restored log drains to normal operation. We will monitor for continued functionality.
-
Official
Resolved
This issue is now 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.