Supabase favicon

Supabase outage on 2026-11-12

supabase.com
November 2026 12 Minor incident

Supabase logged three separate incidents on 12 November 2026, the worst a 3h 6m stretch of database connection errors starting at 20:35 UTC that left some projects unhealthy. All three were provider-side faults, confirmed and closed out on Supabase's own status page.

Started

14:48 UTC

Duration

Lasted 8m

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?

The day's first incident ran from 14:48 to 14:56 UTC and covered two short windows of slow or aborted Storage requests in the eu-west-1 region, already resolved by the time Supabase posted about it. The bigger problem started at 20:35 UTC, when Supabase reported increased connection errors with some databases unavailable and all services showing unhealthy. At 21:42 UTC Supabase widened the scope, saying impact was not limited to the regions first identified, though only a subset of projects were affected. A fix was identified at 22:38 UTC, improvement confirmed at 23:03 UTC, and the incident was marked resolved at 23:40 UTC, giving a total duration of 3h 6m. Overlapping the tail of that, a third incident opened at 22:13 UTC for elevated error rates across Data APIs, Auth, Storage and other HTTP routes in all regions. Supabase's 22:52 UTC update narrowed this down: the error rates traced to a single project with an unusually high request rate, not a widespread fault, and all API routes were already nominal by then. That one closed at 23:31 UTC, 1h 20m after it opened. Supabase lists no components affected in its own breakdown for the day despite describing database, storage and API symptoms directly in the update text. No user reports were filed during the window for any of the three incidents. Across 11 updates, Supabase did not publish a root cause for the connection errors beyond saying a fix was implemented and improvements followed.

Learning

This is a day where the fault sat inside Supabase's own infrastructure, in the database layer and the API gateway, rather than in anything you control. Watching your own application's health checks would not have shown you a unhealthy database connection pool or a quiet storage degradation in eu-west-1, because the problem was happening upstream of your code. Supabase's own account shows the connection errors widened in scope partway through, meaning even their initial diagnosis understated it. The third incident is a good reminder that provider status pages can misattribute scope at first: what looked like an all-regions API problem turned out to be one project's traffic spike, caught and narrowed within forty minutes. None of this appears as user reports in the record, which tells you incidents can run for hours without generating visible complaints, not that they didn't happen. Supabase has logged 58 incidents in the last 90 days with a median duration of 2 hours 4 minutes, so a 3h 6m outage sits 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.