Is Supabase Down?

Partially — Supabase is degraded

Supabase's status page: Open incident · minor incident (“Intermittent 502/503 errors for pg_net calls to Edge Functions”)
FlareWarden checks: Website reachable · 8 of 8 regions · 184 ms

Right now

The verdict is the worse of these two. How we decide

Supabase's status page

status.supabase.com · read 4 minutes ago · checked every 3 minutes

Open incident

minor investigating since 11:12 PM UTC

Intermittent 502/503 errors for pg_net calls to Edge Functions

We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.

Latest update 18 minutes ago

1 location All operational

Open their status page

FlareWarden checks

supabase.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 184 ms
Checked: 16 minutes ago

By region

Amsterdam reachable, 211 ms
Dallas reachable, 238 ms
Frankfurt reachable, 126 ms
Newark reachable, 162 ms
Paris reachable, 177 ms
Stockholm reachable, 161 ms
São Paulo reachable, 137 ms
Toronto reachable, 266 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	8 ms	4 ms	15 ms	176 ms
Dallas	8 ms	0 ms	52 ms	152 ms
Frankfurt	26 ms	1 ms	8 ms	111 ms
Newark	10 ms	4 ms	19 ms	135 ms
Paris	13 ms	10 ms	16 ms	121 ms
Stockholm	10 ms	1 ms	9 ms	129 ms
São Paulo	9 ms	1 ms	7 ms	106 ms
Toronto	10 ms	11 ms	29 ms	151 ms

We check that supabase.com loads, not every feature behind it. Test it yourself

History

Incidents Supabase reported

Since Oct 22, 15 days · from status.supabase.com

Incidents: 14
Major or critical: 3
Median to resolve: 1h 15m

Intermittent 502/503 errors for pg_net calls to Edge Functions
minor · Nov 5
Ongoing
Storage issues in us-east-1 and eu-central-1
minor · Nov 4
lasted 16h 18m
Intermittent errors on Supavisor Shared Pooler in us-east-2
minor · Nov 4
lasted 28m
Management API Postgres config updates overwriting previous updates
Unrated · Nov 3
lasted 2h 8m
Storage uploads failing in us-east-1
minor · Nov 2
lasted 1h 13m
PG15 -> PG17 Upgrade Failures
Unrated · Oct 31
lasted 1h 8m
Logs degraded in multiple regions
Unrated · Oct 30
lasted 51m
Delayed Log Delivery from 14:10 - 15:30 UTC
minor · Oct 28
lasted 52m

And 6 more in this window. Full history on their status page

Supabase website availability

Measured by FlareWarden · supabase.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 197ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of supabase.com from multiple regions every 6 hours. Supabase's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Supabase does

Supabase is an open source backend platform built on Postgres, bundling the database with authentication, file storage, realtime subscriptions and edge functions. Applications use it as their entire backend rather than as one service among many, so an incident usually presents as the whole product failing rather than one feature degrading.

What an outage looks like

Database connections time out or the connection pooler refuses new clients while existing ones continue. Sign-in fails when Auth is affected, locking out new sessions while current ones survive. Storage returns errors on upload and download, so images and attachments break while the rest of the page renders. Realtime subscriptions disconnect and stop delivering changes.

What to do about it

Check status.supabase.com, which reports Database, Auth, Storage, Realtime, Edge Functions, the API Gateway and the Connection Pooler separately, plus compute capacity per AWS region, so match the failing feature to its component and confirm your project's region. Avoid redeploying the application during a platform incident, since a restart discards a working connection pool that would otherwise recover on its own.

Is it down for everyone, or just you?

If this page says Supabase is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Supabase outage FAQ

Is Supabase down or is my project paused?

Free tier projects pause after a period of inactivity and return a distinct error rather than a timeout, and the dashboard shows the paused state plainly. Check status.supabase.com and then your project in the dashboard. A paused project resumes on request within a few minutes and has nothing to do with a platform incident.

Will my data be safe during a Supabase outage?

Committed data lives in Postgres and is not affected by the platform layer becoming unreachable. What fails is your ability to reach it. Writes in flight when the connection dropped may not have committed, and your client will surface those as errors rather than silently discarding them. Availability, not durability, is the thing at risk.

Why is Auth failing when my database queries work?

Auth runs as its own service and is reported as its own component. A failure there blocks new sign-ins and token refreshes while queries made with an existing valid token keep succeeding. That produces a confusing pattern where logged-in users are fine and new visitors cannot get in. Check the Auth component rather than the database.

Does a Supabase incident affect every region?

Rarely. Supabase reports compute capacity per AWS region, and most incidents trace to one region rather than the platform globally. Your project is deployed to a specific region, visible in project settings. An incident in a region you do not use has no effect on you, which is worth confirming before investigating your own code.

Should I restart my app during a Supabase outage?

Usually not. Client libraries hold a connection pool and reconnect as the service returns, so restarting discards that state and adds a reconnection burst to a recovering platform. Restart only if the application has clearly wedged and is no longer retrying after the status page has cleared, rather than as a first response.

How we measure this

We request Supabase's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Supabase publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Supabase itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Supabase goes down

We check Supabase every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required