Supabase favicon

Supabase outage on 2026-11-02

supabase.com
November 2026 2 Minor incident

Supabase's Storage service failed to accept file uploads in the us-east-1 region for 1h 15m on 2 November 2026. If your product stores files for users in that region, this was Supabase's fault, not yours.

Started

21:34 UTC

Duration

Lasted 1h 15m

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 recorded one incident on 2 November 2026, affecting Storage uploads in us-east-1. It started at 21:34 UTC, when Supabase reported that uploads were returning 5xx errors for users in that region. At 21:48 UTC Supabase said it had identified the cause, though it did not name what the cause was. By 22:23 UTC a fix had been implemented and uploads were returning to normal, and Supabase said it would continue monitoring. The incident was marked resolved at 22:48 UTC, a total of 1h 15m after it began. Supabase's status page lists no affected components for this incident, so there is no separate component breakdown to check against the narrative. No user reports were filed during the window on this page, so the only account of what happened is Supabase's own four updates. That is a thin record: four short posts, no explanation of the underlying cause, and no post-mortem published. Supabase runs a busy status page, with 51 incidents in the last 90 days and a median duration of 2 hours 4 minutes, so a 1h 15m Storage incident sits a little faster than its typical fault but is not unusual for the service.

Learning

Supabase did not say what caused the 5xx errors, only that it had identified "the issue" and fixed it, which is typical for a status page update written for speed rather than detail. This incident sat specifically in Storage uploads for one region, so if your own health checks only exercise a database query or an auth call, they would have stayed green while your users' uploads failed. That is the general shape of a regional, component-level outage: the provider's status page can be accurate about what broke while your own monitoring, watching a different part of the same stack, sees nothing wrong. Over the last 30 days UptimeRobot's own checks against Supabase recorded 18 incidents with a median duration of 1h 48m, all resolved, which gives an independent read on how often this kind of thing happens regardless of what Supabase's own page says. 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.