Skip to content

Outage tracker / Auth0

Is Auth0 down?

I'm having a problem

Vendor reports no incidentWhat Auth0 reports

Auth0 reports no incident on its status page.

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

Auth0'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 2 minutes ago

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

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

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:41 PM UTC
US-East848 msChecks passing
US-West575 msChecks passing
Europe476 msChecks passing
Asia-Pacific936 msChecks passing
US-Central452 msChecks passing
Canada737 msChecks passing
UK285 msChecks passing
Southeast Asia1226 msChecks passing
Australia626 msChecks passing
South America638 msChecks passing
their status pagetheir claim, not our reading

Auth0 publishes no status feed we can read, so the only reading here is our check reading on the left.

Auth0 response time, by region

US-East
1.4sp95 · 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 512ms2026-10-08 UTC: p95 555ms2026-10-09 UTC: p95 571ms2026-10-10 UTC: p95 612ms2026-10-11 UTC: p95 596ms2026-10-12 UTC: p95 597ms2026-10-13 UTC: p95 764ms2026-10-14 UTC: p95 646ms2026-10-15 UTC: p95 642ms2026-10-16 UTC: p95 670ms2026-10-17 UTC: p95 754ms2026-10-18 UTC: p95 954ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 965ms2026-10-21 UTC: p95 924ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 247ms2026-10-25 UTC: p95 317ms2026-10-26 UTC: p95 344ms2026-10-27 UTC: p95 800ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 958ms2026-11-01 UTC: p95 877ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 579ms2026-10-08 UTC: p95 503ms2026-10-09 UTC: p95 526ms2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 591ms2026-10-13 UTC: p95 560ms2026-10-14 UTC: p95 681ms2026-10-15 UTC: p95 681ms2026-10-16 UTC: p95 713ms2026-10-17 UTC: p95 637ms2026-10-18 UTC: p95 885ms2026-10-19 UTC: p95 966ms2026-10-20 UTC: p95 810ms2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 708ms2026-10-24 UTC: p95 628ms2026-10-25 UTC: p95 630ms2026-10-26 UTC: p95 715ms2026-10-27 UTC: p95 691ms2026-10-28 UTC: p95 468ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 575ms2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · 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 545ms2026-10-08 UTC: p95 495ms2026-10-09 UTC: p95 734ms2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 743ms2026-10-13 UTC: p95 386ms2026-10-14 UTC: p95 618ms2026-10-15 UTC: p95 540ms2026-10-16 UTC: p95 503ms2026-10-17 UTC: p95 509ms2026-10-18 UTC: p95 603ms2026-10-19 UTC: p95 748ms2026-10-20 UTC: p95 510ms2026-10-21 UTC: p95 702ms2026-10-22 UTC: p95 417ms2026-10-23 UTC: p95 840ms2026-10-24 UTC: p95 667ms2026-10-25 UTC: p95 663ms2026-10-26 UTC: p95 513ms2026-10-27 UTC: p95 502ms2026-10-28 UTC: p95 773ms2026-10-29 UTC: p95 555ms2026-10-30 UTC: p95 698ms2026-10-31 UTC: p95 633ms2026-11-01 UTC: p95 560ms2026-11-02 UTC: p95 690ms2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
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 709ms2026-10-08 UTC: p95 533ms2026-10-09 UTC: p95 774ms2026-10-10 UTC: p95 626ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 591ms2026-10-13 UTC: p95 445ms2026-10-14 UTC: p95 494ms2026-10-15 UTC: p95 527ms2026-10-16 UTC: p95 802ms2026-10-17 UTC: p95 866ms2026-10-18 UTC: p95 644ms2026-10-19 UTC: p95 925ms2026-10-20 UTC: p95 914ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.8s2026-10-28 UTC: p95 890ms2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 885ms2026-11-01 UTC: p95 868ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
US-Central
882msp95 · 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 309ms2026-10-08 UTC: p95 592ms2026-10-09 UTC: p95 497ms2026-10-10 UTC: p95 689ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 726ms2026-10-13 UTC: p95 724ms2026-10-14 UTC: p95 648ms2026-10-15 UTC: p95 693ms2026-10-16 UTC: p95 510ms2026-10-17 UTC: p95 503ms2026-10-18 UTC: p95 228ms2026-10-19 UTC: p95 233ms2026-10-20 UTC: p95 311ms2026-10-21 UTC: p95 677ms2026-10-22 UTC: p95 419ms2026-10-23 UTC: p95 345ms2026-10-24 UTC: p95 211ms2026-10-25 UTC: p95 299ms2026-10-26 UTC: p95 201ms2026-10-27 UTC: p95 428ms2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 904ms2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 953ms2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 882ms
Oct 7Oct 21Nov 5
Canada
1.1sp95 · 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 481ms2026-10-08 UTC: p95 630ms2026-10-09 UTC: p95 562ms2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 928ms2026-10-13 UTC: p95 682ms2026-10-14 UTC: p95 690ms2026-10-15 UTC: p95 709ms2026-10-16 UTC: p95 658ms2026-10-17 UTC: p95 643ms2026-10-18 UTC: p95 595ms2026-10-19 UTC: p95 694ms2026-10-20 UTC: p95 789ms2026-10-21 UTC: p95 841ms2026-10-22 UTC: p95 562ms2026-10-23 UTC: p95 414ms2026-10-24 UTC: p95 315ms2026-10-25 UTC: p95 328ms2026-10-26 UTC: p95 327ms2026-10-27 UTC: p95 605ms2026-10-28 UTC: p95 322ms2026-10-29 UTC: p95 1s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 990ms2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
947msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 542ms2026-10-08 UTC: p95 542ms2026-10-09 UTC: p95 732ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 601ms2026-10-13 UTC: p95 492ms2026-10-14 UTC: p95 512ms2026-10-15 UTC: p95 541ms2026-10-16 UTC: p95 466ms2026-10-17 UTC: p95 771ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 948ms2026-10-21 UTC: p95 750ms2026-10-22 UTC: p95 688ms2026-10-23 UTC: p95 569ms2026-10-24 UTC: p95 842ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 969ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 501ms2026-10-30 UTC: p95 523ms2026-10-31 UTC: p95 516ms2026-11-01 UTC: p95 636ms2026-11-02 UTC: p95 654ms2026-11-03 UTC: p95 388ms2026-11-04 UTC: p95 723ms2026-11-05 UTC: p95 947ms
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 556ms2026-10-08 UTC: p95 714ms2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 693ms2026-10-14 UTC: p95 773ms2026-10-15 UTC: p95 889ms2026-10-16 UTC: p95 674ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 987ms2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Australia
1.5sp95 · 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 341ms2026-10-08 UTC: p95 389ms2026-10-09 UTC: p95 507ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 313ms2026-10-12 UTC: p95 426ms2026-10-13 UTC: p95 466ms2026-10-14 UTC: p95 365ms2026-10-15 UTC: p95 405ms2026-10-16 UTC: p95 418ms2026-10-17 UTC: p95 319ms2026-10-18 UTC: p95 399ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 850ms2026-10-22 UTC: p95 600ms2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 506ms2026-10-26 UTC: p95 246ms2026-10-27 UTC: p95 544ms2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
South America
2.2sp95 · 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 757ms2026-10-08 UTC: p95 810ms2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 906ms2026-10-14 UTC: p95 678ms2026-10-15 UTC: p95 723ms2026-10-16 UTC: p95 611ms2026-10-17 UTC: p95 724ms2026-10-18 UTC: p95 744ms2026-10-19 UTC: p95 756ms2026-10-20 UTC: p95 880ms2026-10-21 UTC: p95 961ms2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 7.9s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 814ms2026-10-30 UTC: p95 875ms2026-10-31 UTC: p95 857ms2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on Auth0

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 Auth0. It cannot diagnose Auth0's own systems.

What we measured, function by function

Auth0 answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

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

Get an email when Auth0 reports an incident

Email me when Auth0 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 Auth0'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: 848msstatus code: 200checked: Nov 5, 2026, 3:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Auth0 normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 575msstatus code: 200checked: Nov 5, 2026, 3:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Auth0 normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 452msstatus code: 200checked: Nov 5, 2026, 3:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Auth0 normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 737msstatus code: 200checked: Nov 5, 2026, 3:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Auth0 normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 638msstatus code: 200checked: Nov 5, 2026, 3:37 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Auth0 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: 476msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Auth0 normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 285msstatus code: 200checked: Nov 5, 2026, 3:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Auth0 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: 936msstatus code: 200checked: Nov 5, 2026, 3:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Auth0 normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1226msstatus code: 200checked: Nov 5, 2026, 3:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Auth0 normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 626msstatus code: 200checked: Nov 5, 2026, 3:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Auth0 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 Auth0, 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 Auth0 yet, which is not evidence that nothing is wrong.

Recent probe events

Planned Maintenancedeclared on their status page2026-11-04
Planned Maintenancedeclared on their status page2026-10-27
Third-Party Outage Impacting US-1 Public Cloud, 6mdeclared on their status page2026-10-23
Planned Maintenance, 189h 25mdeclared on their status page2026-10-19
We have detected an issue., 1mdeclared on their status page2026-10-14
Elevated Errors on Multiple Public Cloud Environments, 31mdeclared on their status page2026-10-14
Elevated Errors on US-4 Public Cloud, 12mdeclared on their status page2026-10-09
Elevated Errors on US-5 Public Cloud, 52mdeclared on their status page2026-09-30

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

We have been measuring Auth0 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 Auth0 covering any window you pick, with our check readings and Auth0's own claim at the time, side by side.

Full check history for Auth0: 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

Auth0 uptime by RealUptime's checksLive, from this page's own readings.
[![Auth0 uptime by RealUptime's checks](https://realuptime.io/outages/auth0/badge.svg?days=30)](https://realuptime.io/outages/auth0)
<a href="https://realuptime.io/outages/auth0"><img src="https://realuptime.io/outages/auth0/badge.svg?days=30" alt="Auth0 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 Auth0 down?", https://realuptime.io/outages/auth0. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: auth surface
https://auth0.auth0.com/.well-known/openid-configuration
secondary
https://status.auth0.com/
secondary
https://auth0.com/

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: auth0.auth0.com

RealUptime is not affiliated with Auth0; the name identifies what we checked, and nothing here speaks for Auth0's own team. We send a single web request to Auth0 from 10 regions on our own schedule and time the response. We do not see inside Auth0's systems, do not use an account or real transaction, and are not the same signal Auth0's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Auth0 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.