Supabase favicon

Supabase outage on 2026-10-19

supabase.com
October 2026 19 Minor incident

On 19 October 2026, Supabase's support ticket creation broke for some customers for 1 hour. This was a fault inside Supabase's own support tooling, not your database or API.

Started

17:13 UTC

Duration

Lasted 1h 0m

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 logged one incident on this day, called "Support Form Errors". It started at 17:13 UTC when Supabase identified that ticket creation was failing for some customers, and said a fix was in development. By 17:36 UTC, Supabase reported the fix was deployed and ticket creation had returned to normal, moving the incident to monitoring. At 18:13 UTC, Supabase resolved it, stating ticket creation had remained normal in the interim. That gives a total duration of 1h 0m, from first identification to resolution. Supabase's status page lists no components as affected, which fits an incident confined to the support form rather than the core platform. There are no user reports filed in this window on the record. The whole incident rests on Supabase's own three updates, there's no independent confirmation beyond what Supabase published. Supabase does not say what caused the ticket creation failure, only that a fix was developed and deployed. Over the past 90 days, Supabase has logged 53 incidents with a median duration of 2 hours 5 minutes, so this one resolved faster than typical. Across all time, Supabase averages 7.5 incidents a month.

Learning

This incident sat in Supabase's support ticketing system, a layer that has nothing to do with your database connections, your API calls, or your authentication flow, so if you run uptime checks against your own endpoints they would have stayed green the entire time, correctly. That's not a gap in your monitoring, it's a reminder that your checks watch your product, not the vendor's internal tooling. A support form failing doesn't touch your users unless they happen to need to file a ticket during that exact hour, which is a narrow and hard to catch window. The lesson here isn't about catching this specific incident, it's about the general shape: provider-side incidents that never touch your infrastructure can still exist and resolve without your monitoring ever knowing. 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.