Storage issues in us-east-1 and eu-central-1
Supabase Storage returns 5XX errors for some customers in us-east-1 and eu-central-1. Supabase reports that the cause is load, that storage response is normal again, and that monitoring continues.
State
Monitoring
Started
Ongoing for
2 h 1 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 22 min 68%
Monitoring
39 min 32%
Updates
Times in UTCAs posted by Supabase
The cause of the issue has been identified as directly related to load. We will be doing maintenance on our platform to address this issue. As of now, storage response has returned to normal. We will continue to monitor the environment.
We are still investigating increased error rates for storage requests, and have expanded the investigation to eu-central-1 as well. The team has identified higher-than-usual load in some areas of the storage infrastructure and is currently working on remediation options.
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
Supabase in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
30
Median duration
1 h 22 min
This incident
1.5× the median
Other Supabase incidents
All incidentsSupabase·Intermittent errors on Supavisor Shared Pooler in us-east-2
Supavisor Shared Pooler in the us-east-2 region had elevated connection errors. Supabase reports that the incident is resolved and that connections are back to normal. The errors were active from 2026-11-04 00:02 UTC to 00:50 UTC.
Supabase·Management API Postgres config updates overwriting previous updates
Supabase reported that Postgres config changes through the Management API only saved the latest values, and earlier changes were overwritten. Supabase disabled some dashboard config changes, deployed a fix, and restored the Connection Logging setting. Supabase resolved the incident after about 2 hours and 8 minutes.
Supabase·Storage uploads failing in us-east-1
Supabase Storage uploads failed with 5xx errors for users in us-east-1. Supabase identified the problem, implemented a fix, and monitored the result. The issue is resolved and it lasted 74 minutes.
Supabase·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
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