Supabase favicon

Supabase outage on 2026-11-06

supabase.com
November 2026 6 Minor incident

Supabase project lifecycle operations in US-West-2 broke for 2h 29m starting at 23:49 UTC. The fault traced back to an upstream provider incident affecting EC2 instances, not to Supabase's own code.

Started

23:49 UTC

Duration

Lasted 2h 29m

Source

IsDown

Next time

Supabase is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

At 23:49 UTC Supabase reported that all Project Lifecycle operations were impacted by an upstream provider incident affecting EC2 instances in US-West-2. That means new project creation, unpauses, restores, project size changes and restarts could all error out, while currently active projects stayed healthy and kept running. Supabase advised against taking any of those lifecycle actions in US-West-2 while it worked with the upstream provider. At 00:26 UTC Supabase posted an update saying there was no new information, lifecycle operations remained impacted, and active projects were still unaffected, with a promise to check back in two hours or sooner. At 01:34 UTC Supabase said the upstream provider had implemented changes and project creation in US-West-2 was recovering, moving the incident to monitoring status. At 02:17 UTC Supabase marked the incident resolved, stating the upstream provider's issue was fixed and lifecycle operations had returned to normal. There is no components list attached to this incident on Supabase's status page. No user reports were filed during the window. Supabase's own filings are the only record of what happened, and they consistently describe a lifecycle layer problem rather than a database or API outage. Over the trailing 90 days Supabase has logged 56 incidents with a median duration of 2 hours 5 minutes, so this one ran close to typical for the provider. Across all time Supabase has filed 480 incidents, averaging 7.6 per month.

Learning

This incident only touched project lifecycle operations, meaning the control plane that creates, pauses, restores and resizes projects, while already-running projects in US-West-2 stayed healthy throughout. If you were only watching your own project's API or database endpoint, you would have seen nothing wrong, because that layer genuinely did not break. The failure sat upstream, in EC2 capacity that Supabase depends on to provision and manage projects, and that is a layer your own uptime checks cannot reach no matter how tightly you configure them. This is the shape to recognise: a provider's control plane can fail while its data plane keeps serving traffic, so a green dashboard on your end and a real incident on theirs are both true at once. If you had tried to spin up a new project or restore one during this window, you would have hit errors that had nothing to do with your code and everything to do with Supabase's upstream provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.