Storage issues in us-east-1 and eu-central-1
Supabase Storage does not work correctly in us-east-1 and eu-central-1. Some customers get 5XX errors on storage requests. Supabase reports higher-than-usual load in parts of the storage infrastructure. The status is investigating, and the team works on remediation options.
State
Investigating
Started
Ongoing for
1 h 12 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 12 min 100%
Updates
Times in UTCAs posted by Supabase
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
About the median
Other Supabase incidents
All incidentsSupabase·Intermittent errors on Supavisor Shared Pooler in us-east-2
Supavisor Shared Pooler had intermittent errors in the us-east-2 region. Supabase reports that the incident is resolved. The incident lasted 29 minutes.
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 overwrote earlier changes. Supabase identified the cause, deployed a fix, and disabled some dashboard config changes during the incident. The incident is resolved and lasted 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 issue, applied a fix, and monitored the result. The incident is resolved and lasted about 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.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