Elevated Error rates for All Supabase project APIs
Supabase reported elevated error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes in all regions. Supabase isolated the errors to one project with a very high request rate. The incident is resolved and lasted 78 minutes.
State
Resolved
Started
Lasted
1 h 18 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
41 min 53%
Monitoring
37 min 47%
Updates
Times in UTCAs posted by Supabase
This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates.
We have isolated the error rates to an individual project with a very unusually high request rate, and we have determined there is no widespread issue as we originally suspected. We will continue to monitor to ensure things remain stable, but all API routes are nominal.
We are currently seeing slightly increased error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes across all regions The team is currently investigating.
Supabase in the last 90 days
Full historyIncidents in 90 days
35
Days with an incident
36
Median duration
1 h 42 min
This incident
24% shorter than the median
Other Supabase incidents
All incidentsSupabase·Database Connection Errors
Supabase reported database connection errors and unavailable databases. The impact was not limited to the regions first identified, and only a subset of projects was affected. Supabase resolved the incident after 3 hours and 4 minutes, and services in all affected regions recovered.
Supabase·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.
Supabase·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.
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