Projects in sa-east-1 experiencing delayed event ingestion
Supabase reports delayed event ingestion for a subset of projects in sa-east-1. Supabase says the issue is recovered and is now monitoring. Project health and uptime were not affected. Users who still see an unhealthy event notification can re-start their project.
State
Monitoring
Started
Ongoing for
6 h 50 min
Worst impact
Notice
Timeline
2 updatesInvestigating
22 min 5%
Monitoring
6 h 29 min 95%
Updates
Times in UTCAs posted by Supabase
The issue has been recovered for projects impacted in sa-east-1. Actual project health or uptime has not been impacted at any time. Users still experiencing an unhealthy event notification on their dashboard can re-start their project to recover. A full fix will be deployed end of today UTC.
EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard. As a workaround, impacted users can re-start their project while we are working on providing a fix.
Supabase in the last 90 days
Full historyIncidents in 90 days
37
Days with an incident
37
Median duration
1 h 42 min
This incident
4.0× the median
Other Supabase incidents
All incidentsSupabase·‘Project not specified’ errors reported for users in ap-northeast-2
Supabase reported "Project not specified" errors for users in ap-northeast-2. Supabase says the issue is resolved. The incident lasted 3 hours and 12 minutes.
Supabase·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.
Supabase·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.
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