Elevated Mgmt API Error Rates in Multiple Regions
This issue has been resolved and our response times are back to operational.
The latest update from Supabase.
State
Resolved
Started
10 d ago
2026-10-22 17:01 UTC
Lasted
4 days
until 2026-10-26 10:16 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
27 min 0%
Identified
30 min 1%
Monitoring
4 days 99%
Updates
Times in UTCAs posted by Supabase
This issue has been resolved and our response times are back to operational.
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
The mitigations have managed the demand spike. We are monitoring for continued stability.
We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
We have noticed issues with requests coming to our API gateway. We are investigating.
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
58× 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
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
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