Supabase reported this minor-impact incident on its official status page on Oct 12, 2026, 19:39 UTC. It was resolved after 5h 51m.
Right now Supabase is operational. Live Supabase status →
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.
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.
We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.
We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.
We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.
We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.
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.
Overlapping incidents aren't necessarily related.
Supabase reported 65 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history