Supabase outage on October 12, 2026: Log ingestion impaired

Supabase reported an incident affecting Supabase for 5 hours 51 minutes on 12 October 2026, from 19:39 to 01:30 UTC.

supabase.com All times UTC

Resolved

Official incident reported by Supabase

Started: 19:39; 12 Oct 2026 UTC
Resolved: 01:30; 13 Oct 2026 UTC
Duration: 5h 51m; 5 hours 51 minutes
Impact: Minor; as rated by Supabase
Updates: 7; posted by Supabase

Timeline

All times UTC.

Official incident from Supabase

Log ingestion impaired

Resolved Minor impact 12 Oct 2026 19:39 UTC View on Supabase's status page

12 Oct 19:39 Official
Investigating
Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.
12 Oct 20:09 Official
Identified
We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.
12 Oct 20:56 Official
Identified
We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.
12 Oct 22:17 Official
Identified
We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.
13 Oct 00:05 Official
Identified
We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.
13 Oct 00:35 Official
Monitoring
The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.
13 Oct 01:30 Official
Resolved
We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

"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.

All Supabase incidents Live Supabase status Every service we track

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.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.