Log ingestion impaired
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 latest update from Supabase.
State
Resolved
Started
19 d ago
2026-10-12 19:39 UTC
Lasted
5 h 51 min
until 2026-10-13 01:30 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
29 min 8%
Identified
4 h 26 min 76%
Monitoring
55 min 16%
Updates
Times in UTCAs posted by Supabase
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.
Supabase in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
27
Median duration
1 h 32 min
This incident
3.8× the median
Other Supabase incidents
All incidentsSupabase·PG15 -> PG17 Upgrade Failures
This issue is now resolved.
Supabase·Logs degraded in multiple regions
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC
This issue has been resolved and log delivery is operational again.
Supabase·Log Drain Issues
This issue is now resolved.
Supabase·Elevated Mgmt API Error Rates in Multiple Regions
This issue has been resolved and our response times are back to operational.
Follow Supabase
Your coding agent knows when Supabase is down, and tells you when a failure is theirs, not yours. You can also get Supabase incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "supabase" and tell me if Supabase has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=supabase/feed subscribe https://outages.cc/feed.xml?providers=supabaseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane