Supabase favicon

Supabase outage on 2026-11-05

supabase.com
November 2026 5 Minor incident

Supabase had a 42 minute window where pg_net calls to Edge Functions in its ap-southeast-1 region returned intermittent 502 and 503 errors. The fault sat on Supabase's side, in the networking layer between Postgres and Edge Functions, not in anything you deployed.

Started

23:12 UTC

Duration

Lasted 42m

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 opened an incident at 23:12 UTC, reporting intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. The symptom was specific: calls made via pg_net, the Postgres extension that lets database functions reach HTTP endpoints, were failing when those endpoints were Edge Functions in that region. Other regions and other call paths were not named as affected. At 23:55 UTC Supabase posted a resolved update, stating that pg_net calls to Edge Functions in ap-southeast-1 were operating normally again. That is the entire public record for this incident: one investigating post and one resolved post, 43 minutes apart, with no interim updates. No components are flagged as affected on the status page for this entry, and no user reports were filed during the window. Supabase's post gives the start and end of the problem but not a cause. Over the past 90 days Supabase has logged 55 incidents with a median duration of 2 hours 4 minutes, so this one resolved faster than typical for the provider. Across all time, Supabase has averaged 7.6 incidents a month over 479 recorded incidents, which gives some sense of how frequently this class of problem surfaces.

Learning

This incident shows a failure specific to one internal call path, pg_net reaching Edge Functions in one region, rather than a broad platform outage. That kind of fault is easy to miss if your own monitoring only checks whether your application responds from the outside, because the symptom lives in a server-to-server call your users never see directly. Supabase's own status page is the only account here, and a single vendor filing carries only as much weight as that vendor gives it, two terse updates with no root cause. Over 22 incidents in the last 30 days, UptimeRobot's own checks against Supabase recorded a median resolution time of 1 hour 47 minutes, all 22 resolved, which is a useful baseline against the 2 hour 4 minute median Supabase itself reports over 90 days. Your own endpoint can look perfectly healthy while a dependency like pg_net quietly fails calls underneath it, and the only way to see that gap is to watch the provider's side as well as your 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.