Edge Function Degradation
Edge function deployments have remained stable. We are closing the incident.
The latest update from Supabase.
State
Resolved
Started
19 d ago
2026-10-12 19:49 UTC
Lasted
22 h 36 min
until 2026-10-13 18:24 UTC
Worst impact
Degraded
Timeline
5 updatesIdentified
6 h 36 min 29%
Monitoring
16 h 71%
Updates
Times in UTCAs posted by Supabase
Edge function deployments have remained stable. We are closing the incident.
Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
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
15× 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