Skip to content

Outage tracker / Supabase

Is Supabase down?

I'm having a problem

Vendor reports no incidentWhat Supabase reports

Supabase reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:39 UTC.

Supabase's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 10 minutes ago

Our checks of Supabase pass from all 10 regions we check.

As of Nov 5, 2026, 3:33 PM UTC, RealUptime's checks of Supabase passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:33 PM UTC
US-East675 msChecks passing
US-West584 msChecks passing
Europe636 msChecks passing
Asia-Pacific1402 msChecks passing
US-Central768 msChecks passing
Canada61 msChecks passing
UK178 msChecks passing
Southeast Asia307 msChecks passing
Australia1324 msChecks passing
South America2044 msChecks passing
their status pagetheir claim, not our reading

Supabase reports: All systems operational (“All Systems Operational”)

from Supabase's own status page, checked Nov 5, 2026, 3:33 PM UTC
Supabase's own status page shows no incident, and our checks of Supabase pass right now.

Supabase's own component breakdown, as they publish it

  • ap-east-1Operational

These are Supabase's components, named and scored by Supabase. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Supabase's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Supabase response time, by region

US-East
1.0sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 402ms2026-10-08 UTC: p95 215ms2026-10-09 UTC: p95 337ms2026-10-10 UTC: p95 319ms2026-10-11 UTC: p95 321ms2026-10-12 UTC: p95 396ms2026-10-13 UTC: p95 365ms2026-10-14 UTC: p95 506ms2026-10-15 UTC: p95 522ms2026-10-16 UTC: p95 570ms2026-10-17 UTC: p95 457ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 83ms2026-10-21 UTC: p95 442ms2026-10-22 UTC: p95 203ms2026-10-23 UTC: p95 208ms2026-10-24 UTC: p95 292ms2026-10-25 UTC: p95 437ms2026-10-26 UTC: p95 163ms2026-10-27 UTC: p95 123ms2026-10-28 UTC: p95 774ms2026-10-29 UTC: p95 875ms2026-10-30 UTC: p95 939ms2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 108ms2026-10-08 UTC: p95 123ms2026-10-09 UTC: p95 367ms2026-10-10 UTC: p95 458ms2026-10-11 UTC: p95 477ms2026-10-12 UTC: p95 460ms2026-10-13 UTC: p95 157ms2026-10-14 UTC: p95 164ms2026-10-15 UTC: p95 175ms2026-10-16 UTC: p95 157ms2026-10-17 UTC: p95 147ms2026-10-18 UTC: p95 106ms2026-10-19 UTC: p95 94ms2026-10-20 UTC: p95 102ms2026-10-21 UTC: p95 201ms2026-10-22 UTC: p95 276ms2026-10-23 UTC: p95 207ms2026-10-24 UTC: p95 102ms2026-10-25 UTC: p95 99ms2026-10-26 UTC: p95 85ms2026-10-27 UTC: p95 225ms2026-10-28 UTC: p95 411ms2026-10-29 UTC: p95 434ms2026-10-30 UTC: p95 599ms2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
1.7sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 354ms2026-10-08 UTC: p95 338ms2026-10-09 UTC: p95 318ms2026-10-10 UTC: p95 302ms2026-10-11 UTC: p95 332ms2026-10-12 UTC: p95 311ms2026-10-13 UTC: p95 123ms2026-10-14 UTC: p95 177ms2026-10-15 UTC: p95 328ms2026-10-16 UTC: p95 329ms2026-10-17 UTC: p95 164ms2026-10-18 UTC: p95 240ms2026-10-19 UTC: p95 158ms2026-10-20 UTC: p95 163ms2026-10-21 UTC: p95 240ms2026-10-22 UTC: p95 267ms2026-10-23 UTC: p95 118ms2026-10-24 UTC: p95 103ms2026-10-25 UTC: p95 112ms2026-10-26 UTC: p95 109ms2026-10-27 UTC: p95 107ms2026-10-28 UTC: p95 194ms2026-10-29 UTC: p95 303ms2026-10-30 UTC: p95 634ms2026-10-31 UTC: p95 571ms2026-11-01 UTC: p95 560ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Asia-Pacific
2.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 494ms2026-10-08 UTC: p95 217ms2026-10-09 UTC: p95 321ms2026-10-10 UTC: p95 371ms2026-10-11 UTC: p95 311ms2026-10-12 UTC: p95 415ms2026-10-13 UTC: p95 692ms2026-10-14 UTC: p95 233ms2026-10-15 UTC: p95 333ms2026-10-16 UTC: p95 458ms2026-10-17 UTC: p95 973ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 3.5s2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 880ms2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 3s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
US-Central
896msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 134ms2026-10-08 UTC: p95 318ms2026-10-09 UTC: p95 157ms2026-10-10 UTC: p95 127ms2026-10-11 UTC: p95 190ms2026-10-12 UTC: p95 455ms2026-10-13 UTC: p95 137ms2026-10-14 UTC: p95 142ms2026-10-15 UTC: p95 304ms2026-10-16 UTC: p95 160ms2026-10-17 UTC: p95 119ms2026-10-18 UTC: p95 143ms2026-10-19 UTC: p95 107ms2026-10-20 UTC: p95 152ms2026-10-21 UTC: p95 330ms2026-10-22 UTC: p95 238ms2026-10-23 UTC: p95 131ms2026-10-24 UTC: p95 121ms2026-10-25 UTC: p95 177ms2026-10-26 UTC: p95 118ms2026-10-27 UTC: p95 118ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 250ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 896ms
Oct 7Oct 21Nov 5
Canada
1.8sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 149ms2026-10-08 UTC: p95 107ms2026-10-09 UTC: p95 104ms2026-10-10 UTC: p95 127ms2026-10-11 UTC: p95 164ms2026-10-12 UTC: p95 100ms2026-10-13 UTC: p95 121ms2026-10-14 UTC: p95 141ms2026-10-15 UTC: p95 116ms2026-10-16 UTC: p95 374ms2026-10-17 UTC: p95 489ms2026-10-18 UTC: p95 92ms2026-10-19 UTC: p95 102ms2026-10-20 UTC: p95 91ms2026-10-21 UTC: p95 564ms2026-10-22 UTC: p95 417ms2026-10-23 UTC: p95 127ms2026-10-24 UTC: p95 118ms2026-10-25 UTC: p95 93ms2026-10-26 UTC: p95 129ms2026-10-27 UTC: p95 772ms2026-10-28 UTC: p95 180ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 167ms2026-11-04 UTC: p95 808ms2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
UK
657msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 133ms2026-10-08 UTC: p95 191ms2026-10-09 UTC: p95 308ms2026-10-10 UTC: p95 368ms2026-10-11 UTC: p95 404ms2026-10-12 UTC: p95 340ms2026-10-13 UTC: p95 105ms2026-10-14 UTC: p95 128ms2026-10-15 UTC: p95 111ms2026-10-16 UTC: p95 102ms2026-10-17 UTC: p95 522ms2026-10-18 UTC: p95 583ms2026-10-19 UTC: p95 672ms2026-10-20 UTC: p95 406ms2026-10-21 UTC: p95 166ms2026-10-22 UTC: p95 161ms2026-10-23 UTC: p95 129ms2026-10-24 UTC: p95 94ms2026-10-25 UTC: p95 116ms2026-10-26 UTC: p95 107ms2026-10-27 UTC: p95 843ms2026-10-28 UTC: p95 864ms2026-10-29 UTC: p95 475ms2026-10-30 UTC: p95 228ms2026-10-31 UTC: p95 225ms2026-11-01 UTC: p95 164ms2026-11-02 UTC: p95 407ms2026-11-03 UTC: p95 490ms2026-11-04 UTC: p95 462ms2026-11-05 UTC: p95 657ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 173ms2026-10-08 UTC: p95 142ms2026-10-09 UTC: p95 144ms2026-10-10 UTC: p95 177ms2026-10-11 UTC: p95 186ms2026-10-12 UTC: p95 310ms2026-10-13 UTC: p95 132ms2026-10-14 UTC: p95 158ms2026-10-15 UTC: p95 146ms2026-10-16 UTC: p95 155ms2026-10-17 UTC: p95 624ms2026-10-18 UTC: p95 495ms2026-10-19 UTC: p95 631ms2026-10-20 UTC: p95 139ms2026-10-21 UTC: p95 322ms2026-10-22 UTC: p95 554ms2026-10-23 UTC: p95 397ms2026-10-24 UTC: p95 302ms2026-10-25 UTC: p95 208ms2026-10-26 UTC: p95 214ms2026-10-27 UTC: p95 509ms2026-10-28 UTC: p95 472ms2026-10-29 UTC: p95 508ms2026-10-30 UTC: p95 980ms2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Australia
1.6sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 361ms2026-10-08 UTC: p95 388ms2026-10-09 UTC: p95 433ms2026-10-10 UTC: p95 438ms2026-10-11 UTC: p95 617ms2026-10-12 UTC: p95 485ms2026-10-13 UTC: p95 280ms2026-10-14 UTC: p95 260ms2026-10-15 UTC: p95 239ms2026-10-16 UTC: p95 262ms2026-10-17 UTC: p95 565ms2026-10-18 UTC: p95 749ms2026-10-19 UTC: p95 624ms2026-10-20 UTC: p95 254ms2026-10-21 UTC: p95 523ms2026-10-22 UTC: p95 684ms2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 973ms2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 950ms2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
South America
1.8sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 380ms2026-10-08 UTC: p95 432ms2026-10-09 UTC: p95 427ms2026-10-10 UTC: p95 418ms2026-10-11 UTC: p95 418ms2026-10-12 UTC: p95 392ms2026-10-13 UTC: p95 212ms2026-10-14 UTC: p95 309ms2026-10-15 UTC: p95 266ms2026-10-16 UTC: p95 259ms2026-10-17 UTC: p95 354ms2026-10-18 UTC: p95 175ms2026-10-19 UTC: p95 181ms2026-10-20 UTC: p95 252ms2026-10-21 UTC: p95 596ms2026-10-22 UTC: p95 366ms2026-10-23 UTC: p95 5.0s2026-10-24 UTC: p95 198ms2026-10-25 UTC: p95 249ms2026-10-26 UTC: p95 387ms2026-10-27 UTC: p95 185ms2026-10-28 UTC: p95 265ms2026-10-29 UTC: p95 660ms2026-10-30 UTC: p95 816ms2026-10-31 UTC: p95 992ms2026-11-01 UTC: p95 694ms2026-11-02 UTC: p95 980ms2026-11-03 UTC: p95 720ms2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on Supabase

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Supabase. It cannot diagnose Supabase's own systems.

Email me when Supabase reports an incident on its status page, and again when it reports it resolved.

Get an email when Supabase reports an incident

Email me when Supabase reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Supabase's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 675msstatus code: 401checked: Nov 5, 2026, 3:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Supabase normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 584msstatus code: 401checked: Nov 5, 2026, 3:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Supabase normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 768msstatus code: 401checked: Nov 5, 2026, 3:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Supabase normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 61msstatus code: 401checked: Nov 5, 2026, 3:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Supabase normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2044msstatus code: 401checked: Nov 5, 2026, 3:16 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Supabase normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 636msstatus code: 401checked: Nov 5, 2026, 3:30 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Supabase normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 178msstatus code: 401checked: Nov 5, 2026, 3:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Supabase normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1402msstatus code: 401checked: Nov 5, 2026, 3:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Supabase normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 307msstatus code: 401checked: Nov 5, 2026, 3:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Supabase normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1324msstatus code: 401checked: Nov 5, 2026, 3:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Supabase normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Supabase, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Supabase yet, which is not evidence that nothing is wrong.

Recent probe events

Storage issues in us-east-1 and eu-central-1, 16h 18mdeclared on their status page2026-11-04
Intermittent errors on Supavisor Shared Pooler in us-east-2, 29mdeclared on their status page2026-11-04
Management API Postgres config updates overwriting previous updates, 2h 8mdeclared on their status page2026-11-03
Storage uploads failing in us-east-1, 1h 14mdeclared on their status page2026-11-02
PG15 -> PG17 Upgrade Failures, 1h 8mdeclared on their status page2026-10-31
Logs degraded in multiple regions, 51mdeclared on their status page2026-10-30
Delayed Log Delivery from 14:10 - 15:30 UTC, 53mdeclared on their status page2026-10-28
Log Drain Issues, 47mdeclared on their status page2026-10-22

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Supabase since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Supabase covering any window you pick, with our check readings and Supabase's own claim at the time, side by side.

Full check history for Supabase: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Supabase uptime by RealUptime's checksLive, from this page's own readings.
[![Supabase uptime by RealUptime's checks](https://realuptime.io/outages/supabase/badge.svg?days=30)](https://realuptime.io/outages/supabase)
<a href="https://realuptime.io/outages/supabase"><img src="https://realuptime.io/outages/supabase/badge.svg?days=30" alt="Supabase uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Supabase down?", https://realuptime.io/outages/supabase. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://api.supabase.com/v1/projects
secondary
https://status.supabase.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.supabase.com

RealUptime is not affiliated with Supabase; the name identifies what we checked, and nothing here speaks for Supabase's own team. We send a single web request to Supabase from 10 regions on our own schedule and time the response. We do not see inside Supabase's systems, do not use an account or real transaction, and are not the same signal Supabase's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Supabase is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.