Supabase favicon

Supabase outage on 2026-11-04

supabase.com
November 2026 4 Minor incident

Supabase had two separate incidents on 4 November 2026: a brief pooler failure in us-east-2 and a much longer storage problem spanning us-east-1 and eu-central-1. Both were on Supabase's side of the connection, the second one lasting 16h 21m before resolution.

Started

03:48 UTC

Duration

Lasted 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?

The day started at 03:48 UTC with Supabase reporting elevated errors on the Supavisor Shared Pooler in us-east-2, referencing a window that actually began at 00:02 UTC. The error example shown was a checkout failure with a database connection timeout, consistent with clients unable to get a pooled connection. That incident resolved quickly, with Supabase marking it resolved at 04:17 UTC, 29 minutes after the update was posted. A second, larger incident started at 18:43 UTC, when Supabase identified 5XX errors on Storage in us-east-1. By 19:18 UTC the investigation had expanded to eu-central-1, with Supabase citing higher-than-usual load on storage infrastructure. At 20:05 UTC Supabase said the cause was load-related and that storage response had returned to normal, but the incident stayed open under monitoring. Supabase then scheduled maintenance for 5 November between 08:00 and 09:00 UTC to address the underlying capacity issue, warning of a possible short interruption limited to us-east-1. That maintenance ran as planned, completing at 08:06 UTC, with Supabase noting some requests may have failed briefly during the database switchover. The incident was formally resolved at 11:02 UTC, giving a total duration of 16h 21m. No component list beyond the named regions and services was published, and no user reports were logged in the window for either incident. Everything on this page comes from Supabase's own status updates, there is no independent confirmation beyond what they chose to post.

Learning

Supabase's own updates describe both incidents as infrastructure-side: a pooler connection failure in one region, and a storage load problem that needed a scheduled database capacity change to actually fix. Neither of these is something you'd catch by watching your own application logs alone, since from your side it just looks like database timeouts or failed storage requests with no obvious pattern. An external check against Supabase's endpoints during these windows would have shown exactly what Supabase's status page shows: errors tied to specific regions and specific services, not your code. That's the useful split to remember. Your own monitoring tells you your product is unreachable, but it can't tell you whether the fault sits in your deployment or in the provider you depend on. Supabase's history here isn't unusual by their own numbers, 54 incidents in 90 days with a typical duration around two hours, so a 16-hour one stands out and is worth noting if it recurs. 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.