Edge Function Issues in ap-northeast-1
Supabase Edge Functions did not work correctly in the ap-northeast-1 region. Supabase reports that the issue is resolved. The outage lasted about 3 hours and 7 minutes.
State
Resolved
Started
Lasted
3 h 7 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
1 h 39 min 53%
Monitoring
1 h 28 min 47%
Updates
Times in UTCAs posted by Supabase
The mitigation has successfully restored Edge Functions to normal operation in ap-northeast-1. This issue is resolved.
The mitigations have returned functions response to normal. We will continue to monitor for stability.
We have implemented a mitigation to stabilize the functions service.
We have identified an increase in edge function errors in ap-northeast-1, we continue to investigate.
We experienced an issue with edge functions in ap-northeast-1 between 20:00 and 20:10 UTC, we are investigating.
Supabase in the last 90 days
Full historyIncidents in 90 days
38
Days with an incident
37
Median duration
1 h 52 min
This incident
1.7× 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·Projects in sa-east-1 experiencing delayed event ingestion
Supabase reports delayed event ingestion for projects in sa-east-1. Some projects showed an unhealthy status in the Dashboard. Supabase marked the incident resolved. The incident lasted about 8 hours and 44 minutes. Impacted users can re-start their project as a workaround.
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.
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