Supabase favicon

Supabase outage on 2026-11-08

supabase.com
November 2026 8 Minor incident

Supabase's Supavisor connection pooler in eu-west-2 broke for a stretch on 8 November 2026. Supabase says the interruption actually ran from 09:42 to 09:52 GMT, though its own public filing and resolution took until 12:35 to close out, 1h 45m after the first update went up.

Started

10:53 UTC

Duration

Lasted 1h 45m

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's status page logged one incident on 8 November 2026, titled "Interruption in connections to Supavisor in eu-west-2". The first update, posted at 10:53 UTC, says connections to Supavisor were interrupted between 09:42 and 09:52 GMT, and that this "may have affected connections for some users". That phrasing means Supabase was already describing the problem in the past tense when it told you about it: the fault had come and gone before the first public word reached the status page. Supabase moved to a monitoring state at that point, saying the issue had been resolved and it was watching to confirm recovery. The incident was marked resolved at 12:35 UTC, with Supabase stating monitoring had confirmed systems operating normally. That gives a total window of 1h 45m from first notice to resolution, even though the actual connection interruption described inside that window lasted around ten minutes. No components are listed as affected on the status page for this incident, and no user reports were filed during the window on the record here. There are only two updates in total for this incident, both quoted above in full, so what you see here is the entirety of what Supabase published. No post-mortem has been issued and no cause is given beyond the description of what broke.

Learning

This incident sits specifically at the connection pooler layer, Supavisor, which sits between your application and your Postgres database on Supabase's side. If your own uptime checks hit a simple HTTP endpoint or your frontend, they would not necessarily catch a ten-minute pooler interruption that happened and resolved before most synthetic checks would even have fired a second probe. UptimeRobot's 30 day data for Supabase shows 21 incidents in that window, all resolved, with a median duration of 1h 45m, the same figure as today's total window, which tells you this kind of short, self-resolving connection fault is a regular pattern for Supabase rather than a one-off. Supabase's own 90 day history lists 57 incidents with a median duration of 2 hours 4 minutes, and its all-time rate runs at 7.6 incidents a month, so a database layer fault like this one is not rare. The lesson is that your monitoring of your own application tells you whether your product is reachable, but it cannot tell you whether the database connection layer underneath it briefly dropped and recovered on its own. 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.