Project Lifecycle Issues in eu-west-1
This incident has been resolved.
The latest update from Supabase.
State
Resolved
Started
38 d ago
2026-09-24 15:36 UTC
Lasted
2 h 2 min
until 2026-09-24 17:38 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
14 min 12%
Identified
1 h 22 min 67%
Monitoring
25 min 21%
Updates
Times in UTCAs posted by Supabase
This incident has been resolved.
We are continuing to monitor to ensure ongoing stability.
The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
We are investigating project lifecycle operation issues in eu-west-1.
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
1.3× 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