Increased Errors with Project Lifecycle Operations in US-West-2
Supabase reports increased errors with Project Lifecycle operations in US-West-2. The affected operations include project creation, unpauses, restores, project size changes, and restarts. Active projects continue to work. Supabase has identified an upstream provider incident that affects EC2 instances in US-West-2. Supabase advises against these actions in US-West-2 at this time.
State
Identified
Started
Ongoing for
1 h
Worst impact
Degraded
Timeline
2 updatesIdentified
1 h 100%
Updates
Times in UTCAs posted by Supabase
We continue to work with our upstream provider as they investigate the ongoing incident affecting US-West-2. There are no additional updates at this time, and Project Lifecycle operations remain impacted. Currently active projects remain unaffected. We will provide another update in 2 hours, or sooner if additional information becomes available.
All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.
Supabase in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
33
Median duration
1 h 22 min
This incident
27% shorter than the median
Other Supabase incidents
All incidentsSupabase·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.
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 earlier changes were overwritten. Supabase disabled some dashboard config changes, deployed a fix, and restored the Connection Logging setting. Supabase resolved the incident after about 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 problem, implemented a fix, and monitored the result. The issue is resolved and it lasted 74 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