Storage request degradation in eu-west-1
Supabase Storage requests were slow or failed in the eu-west-1 region. Supabase reports that the incident is resolved after 8 minutes.
State
Resolved
Started
Lasted
8 min
Worst impact
Degraded
Timeline
2 updatesMonitoring
8 min 100%
Updates
Times in UTCAs posted by Supabase
We have mitigated the issue with the Storage service and we have not observed any further issues during our monitoring period. We consider this incident to be resolved.
Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.
Supabase in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
36
Median duration
1 h 42 min
This incident
92% shorter than the median
Other Supabase incidents
All incidentsSupabase·Project Lifecycle Issues in ap-northeast-1
Project lifecycle operations did not work in the ap-northeast-1 region. Supabase reported the incident as resolved after 4 hours and 48 minutes.
Supabase·Interruption in connections to Supavisor in eu-west-2
Supavisor connections in the eu-west-2 region did not work for some users. Supabase reports that the incident is resolved. The interruption lasted about 102 minutes.
Supabase·Increased Errors with Project Lifecycle Operations in US-West-2
Supabase reported errors with Project Lifecycle operations in US-West-2. These operations include project creation, unpauses, restore actions, project size changes, and restarts. Supabase marked the incident as resolved. The outage lasted 2 hours and 28 minutes.
Supabase·Intermittent 502/503 errors for pg_net calls to Edge Functions
Supabase reported intermittent 502 and 503 errors for pgnet calls to Edge Functions in ap-southeast-1. Supabase resolved the issue. The outage lasted 42 minutes.
Supabase·Storage issues in us-east-1 and eu-central-1
Supabase Storage had degraded service and 5XX errors in us-east-1 and eu-central-1. Supabase later identified the cause as load, and storage returned to normal. Supabase resolved the incident on 5 November 2026 after 16 hours and 18 minutes.
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.live/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.live/feed.xml?providers=supabase/feed subscribe https://outages.live/feed.xml?providers=supabaseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane