outages.live
Live
SupabaseIncident · 2026-10-22 18:03 UTC

Log Drain Issues

ResolvedOfficial update

This issue is now resolved.

The latest update from Supabase.

State

Resolved

Started

10 d ago

2026-10-22 18:03 UTC

Lasted

47 min

until 2026-10-22 18:50 UTC

Worst impact

Degraded

Timeline

3 updates
18:0318:1518:2718:3818:50
DegradedUpdate postedTimes in UTC

Investigating

19 min 41%

Monitoring

28 min 59%

Updates

Times in UTC

As posted by Supabase

Resolved2026-10-22 18:50 UTC

This issue is now resolved.

Monitoring2026-10-22 18:22 UTC

The rollback has restored log drains to normal operation. We will monitor for continued functionality.

Investigating2026-10-22 18:03 UTC

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.

Supabase in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

27

Median duration

1 h 32 min

This incident

49% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 1 h 32 min
90 days agoToday

Other Supabase incidents

All incidents

Supabase·PG15 -> PG17 Upgrade Failures

This issue is now resolved.

Resolvedresolved 11 h ago

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

Resolvedresolved 2 d ago

Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC

This issue has been resolved and log delivery is operational again.

Resolvedresolved 4 d ago

Supabase·Elevated Mgmt API Error Rates in Multiple Regions

This issue has been resolved and our response times are back to operational.

Resolvedresolved 6 d ago

Supabase·Elevated Mgmt API Error Rates in Multiple Regions

Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.

Resolvedresolved 10 d ago

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.

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

RSS
https://outages.cc/feed.xml?providers=supabase
Slack
/feed subscribe https://outages.cc/feed.xml?providers=supabase

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane