Skip to main content
Supabase logo

Is Supabase Down?

No — Supabase is up

Reachable from all 8 checked regions

Average response time: 127ms

Last checked · checks run every 6 hours

Official status page: https://status.supabase.com

401 errors due to JWT rejections

minor identified

Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.

Components the vendor reports as affected: API Gateway Degraded Performance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Supabase fail from enough regions to rule out probe noise.

Supabase uptime

100%
Last 7 days
99.85%
Last 30 days
99.85%
Last 90 days
161ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

17-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 97.50% uptime, 40 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 31 checks
Aug 3: 100.00% uptime, 31 checks
Aug 4: 100.00% uptime, 38 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 24 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 40 checks
Aug 14: 100.00% uptime, 32 checks, 1 incident
Aug 15: 100.00% uptime, 39 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
120ms
DNS 16ms TCP 0ms TLS 18ms TTFB 98ms
arn
121ms
DNS 10ms TCP 0ms TLS 9ms TTFB 86ms
bom
131ms
DNS 16ms TCP 1ms TLS 8ms TTFB 89ms
nrt
96ms
DNS 5ms TCP 1ms TLS 8ms TTFB 82ms
ord
219ms
DNS 16ms TCP 12ms TLS 17ms TTFB 139ms
sin
122ms
DNS 10ms TCP 2ms TLS 9ms TTFB 97ms
sjc
89ms
DNS 6ms TCP 1ms TLS 6ms TTFB 76ms
syd
97ms
DNS 8ms TCP 2ms TLS 6ms TTFB 81ms
yyz
117ms
DNS 7ms TCP 0ms TLS 19ms TTFB 90ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Supabase goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required