Supabase favicon

Supabase outage on 2026-10-30

supabase.com
October 2026 30 Minor incident

Supabase's Logs functionality degraded across multiple regions for 52 minutes on 30 October 2026. The fault sat in logging infrastructure, not your database or APIs, and Supabase says so directly on its own status page.

Started

11:38 UTC

Duration

Lasted 52m

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 an incident at 11:38 UTC, reporting degraded Logs functionality in multiple regions. The first update said some users might see delayed, missing, or unavailable logs in the Dashboard and Logs API, and stated plainly that other services, including your database and APIs, were not affected at that time. At 11:56 Supabase said it had identified the cause and a fix was being prepared, though it did not say publicly what the cause was. A fix was deployed by 12:11, with the team monitoring the log service from that point. The incident was marked resolved at 12:29, with Supabase noting that smoke tests completed successfully at 12:20 UTC. Total time from first report to resolution was 52 minutes. This record covers one incident with four updates, moving cleanly through investigating, identified, monitoring, and resolved. No components list was published alongside this incident. No user reports were filed in the window covered by this record. Supabase's own wording throughout is specific: logs, not database, not APIs. That distinction matters because it tells you what to check first if you saw something odd during this window. Over the past 90 days Supabase has logged 50 incidents with a median duration of 2 hours 9 minutes, so this one resolved faster than most. Across all time Supabase has recorded 473 incidents, averaging 7.5 per month.

Learning

This incident sat entirely inside Supabase's logging layer, the part of the stack that records what happened rather than the part that serves your requests. Supabase's own update said your database and APIs were unaffected, so a health check against your actual endpoints during this window would have come back green, correctly. That is not a contradiction. An uptime check watches whether your product answers, and your product kept answering. What it would not have shown you is that your dashboard view into what your backend was doing had gone dark, which matters if you were relying on logs to debug something else at the same time. This is the general shape of a logging or observability outage: the service still runs, but your visibility into it does not. Watching only your own endpoints tells you your product is up, it does not tell you whether the provider's internal tooling is giving you an accurate picture. 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.