Supabase favicon

Supabase outage on 2026-11-11

supabase.com
November 2026 11 Minor incident

Project lifecycle operations in Supabase's ap-northeast-1 region broke for 4 hours and 50 minutes on 11 November 2026. The fault sat with an upstream provider, not with Supabase's own code.

Started

16:44 UTC

Duration

Lasted 4h 50m

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?

Supabase opened this incident at 16:44 UTC, reporting that project lifecycle operations in ap-northeast-1 were impacted. That category covers the actions you'd use to create, pause, resume or otherwise manage a project rather than query a live database, so the practical effect was on project management, not necessarily on every running database in the region. At 17:05 Supabase said the issue had been identified by their upstream provider and was being addressed, which tells you the root cause sat outside Supabase's own stack from early on. At 18:14 Supabase reported the upstream provider was seeing improvements, but added that they were internally validating recovery before re-enabling functionality, a sign that Supabase chose to hold the gate shut rather than trust the upstream fix immediately. By 18:39 they said project operations were recovering and that they would keep monitoring until things stabilised. The incident was marked resolved at 21:32 UTC, with Supabase stating that operations had returned to normal and remained stable. No component list was published alongside this incident, so there is no breakdown of which specific services inside Supabase were marked affected. No user reports were filed during the window, and Supabase's status page is the only account of what happened. There is nothing on record to explain which upstream provider was involved or what the underlying fault was. No post-mortem has been published for this incident.

Learning

This incident sat in project lifecycle management, the layer that handles creating, pausing and resuming projects, which is a different layer from the live database connections that uptime checks against your own endpoints would typically watch. If your product only pings its own API or database and that database was already running, your monitoring would have stayed green through this entire window, because the running database wasn't what broke. What broke was the control layer sitting above it, managed by an upstream provider Supabase depends on, and that kind of fault is invisible to checks aimed at your application's surface. Supabase's own staged response, identifying the issue, waiting for upstream recovery, then internally validating before re-enabling functionality, shows the fix wasn't instant even once the root cause was found elsewhere. Over the last 90 days Supabase has logged 57 incidents with a median duration of 2 hours 4 minutes, so a project lifecycle disruption lasting the better part of five hours sits well above typical. 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.