Project Lifecycle Issues in ap-northeast-1
Supabase reports that project lifecycle operations do not work in ap-northeast-1. Supabase identified the issue and the upstream provider is addressing it. The incident started 22 minutes ago.
State
Identified
Started
Ongoing for
1 h 5 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
22 min 34%
Identified
43 min 66%
Updates
Times in UTCAs posted by Supabase
The issue has been identified by our upstream provider and is being addressed.
Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.
Supabase in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
35
Median duration
1 h 42 min
This incident
36% shorter than the median
Other Supabase incidents
All incidentsSupabase·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.
Supabase·Intermittent 502/503 errors for pg_net calls to Edge Functions
Supabase reported intermittent 502 and 503 errors for pgnet calls to Edge Functions in ap-southeast-1. Supabase resolved the issue. The outage lasted 42 minutes.
Supabase·Storage issues in us-east-1 and eu-central-1
Supabase Storage had degraded service and 5XX errors in us-east-1 and eu-central-1. Supabase later identified the cause as load, and storage returned to normal. Supabase resolved the incident on 5 November 2026 after 16 hours and 18 minutes.
Supabase·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.
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