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-10-19 21:26 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 1 minute ago

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

As of Oct 19, 2026, 9:26 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 Oct 19, 2026, 9:26 PM UTC
US-East967 msChecks passing
US-West739 msChecks passing
Europe367 msChecks passing
Asia-Pacific895 msChecks passing
US-Central132 msChecks passing
Canada399 msChecks passing
UK370 msChecks passing
Southeast Asia372 msChecks passing
Australia593 msChecks passing
South America736 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.2sp95 · 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-09-20 UTC: p95 321ms2026-09-21 UTC: p95 256ms2026-09-22 UTC: p95 198ms2026-09-23 UTC: p95 225ms2026-09-24 UTC: p95 251ms2026-09-25 UTC: p95 220ms2026-09-26 UTC: p95 289ms2026-09-27 UTC: p95 495ms2026-09-28 UTC: p95 485ms2026-09-29 UTC: p95 328ms2026-09-30 UTC: p95 309ms2026-10-01 UTC: p95 544ms2026-10-02 UTC: p95 516ms2026-10-03 UTC: p95 587ms2026-10-04 UTC: p95 652ms2026-10-05 UTC: p95 559ms2026-10-06 UTC: p95 486ms2026-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.2s
Sep 20Oct 4Oct 19
US-West
966msp95 · 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-09-20 UTC: p95 500ms2026-09-21 UTC: p95 499ms2026-09-22 UTC: p95 503ms2026-09-23 UTC: p95 496ms2026-09-24 UTC: p95 523ms2026-09-25 UTC: p95 425ms2026-09-26 UTC: p95 500ms2026-09-27 UTC: p95 391ms2026-09-28 UTC: p95 461ms2026-09-29 UTC: p95 508ms2026-09-30 UTC: p95 339ms2026-10-01 UTC: p95 275ms2026-10-02 UTC: p95 309ms2026-10-03 UTC: p95 471ms2026-10-04 UTC: p95 529ms2026-10-05 UTC: p95 522ms2026-10-06 UTC: p95 575ms2026-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 966ms
Sep 20Oct 4Oct 19
Europe
776msp95 · 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-09-20 UTC: p95 610ms2026-09-21 UTC: p95 608ms2026-09-22 UTC: p95 823ms2026-09-23 UTC: p95 756ms2026-09-24 UTC: p95 775ms2026-09-25 UTC: p95 795ms2026-09-26 UTC: p95 767ms2026-09-27 UTC: p95 622ms2026-09-28 UTC: p95 645ms2026-09-29 UTC: p95 582ms2026-09-30 UTC: p95 565ms2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 506ms2026-10-03 UTC: p95 658ms2026-10-04 UTC: p95 488ms2026-10-05 UTC: p95 480ms2026-10-06 UTC: p95 455ms2026-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 776ms
Sep 20Oct 4Oct 19
Asia-Pacific
892msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 590ms2026-09-21 UTC: p95 575ms2026-09-22 UTC: p95 707ms2026-09-23 UTC: p95 833ms2026-09-24 UTC: p95 796ms2026-09-25 UTC: p95 531ms2026-09-26 UTC: p95 611ms2026-09-27 UTC: p95 439ms2026-09-28 UTC: p95 503ms2026-09-29 UTC: p95 284ms2026-09-30 UTC: p95 479ms2026-10-01 UTC: p95 611ms2026-10-02 UTC: p95 643ms2026-10-03 UTC: p95 646ms2026-10-04 UTC: p95 756ms2026-10-05 UTC: p95 766ms2026-10-06 UTC: p95 758ms2026-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 892ms
Sep 20Oct 4Oct 19
US-Central
209msp95 · 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-09-20 UTC: p95 211ms2026-09-21 UTC: p95 212ms2026-09-22 UTC: p95 297ms2026-09-23 UTC: p95 527ms2026-09-24 UTC: p95 564ms2026-09-25 UTC: p95 396ms2026-09-26 UTC: p95 459ms2026-09-27 UTC: p95 382ms2026-09-28 UTC: p95 405ms2026-09-29 UTC: p95 425ms2026-09-30 UTC: p95 607ms2026-10-01 UTC: p95 783ms2026-10-02 UTC: p95 449ms2026-10-03 UTC: p95 370ms2026-10-04 UTC: p95 246ms2026-10-05 UTC: p95 243ms2026-10-06 UTC: p95 270ms2026-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 209ms
Sep 20Oct 4Oct 19
Canada
679msp95 · 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-09-20 UTC: p95 414ms2026-09-21 UTC: p95 324ms2026-09-22 UTC: p95 558ms2026-09-23 UTC: p95 533ms2026-09-24 UTC: p95 398ms2026-09-25 UTC: p95 404ms2026-09-26 UTC: p95 361ms2026-09-27 UTC: p95 463ms2026-09-28 UTC: p95 479ms2026-09-29 UTC: p95 334ms2026-09-30 UTC: p95 243ms2026-10-01 UTC: p95 285ms2026-10-02 UTC: p95 226ms2026-10-03 UTC: p95 293ms2026-10-04 UTC: p95 416ms2026-10-05 UTC: p95 419ms2026-10-06 UTC: p95 431ms2026-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 679ms
Sep 20Oct 4Oct 19
UK
1.3sp95 · 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-09-20 UTC: p95 494ms2026-09-21 UTC: p95 484ms2026-09-22 UTC: p95 596ms2026-09-23 UTC: p95 514ms2026-09-24 UTC: p95 567ms2026-09-25 UTC: p95 455ms2026-09-26 UTC: p95 496ms2026-09-27 UTC: p95 456ms2026-09-28 UTC: p95 548ms2026-09-29 UTC: p95 333ms2026-09-30 UTC: p95 310ms2026-10-01 UTC: p95 568ms2026-10-02 UTC: p95 477ms2026-10-03 UTC: p95 397ms2026-10-04 UTC: p95 560ms2026-10-05 UTC: p95 579ms2026-10-06 UTC: p95 592ms2026-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.3s
Sep 20Oct 4Oct 19
Southeast Asia
1.9sp95 · 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-09-20 UTC: p95 949ms2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 983ms2026-09-27 UTC: p95 723ms2026-09-28 UTC: p95 943ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 840ms2026-10-01 UTC: p95 549ms2026-10-02 UTC: p95 579ms2026-10-03 UTC: p95 500ms2026-10-04 UTC: p95 545ms2026-10-05 UTC: p95 519ms2026-10-06 UTC: p95 489ms2026-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.9s
Sep 20Oct 4Oct 19
Australia
449msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 947ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 917ms2026-09-23 UTC: p95 794ms2026-09-24 UTC: p95 567ms2026-09-25 UTC: p95 483ms2026-09-26 UTC: p95 666ms2026-09-27 UTC: p95 530ms2026-09-28 UTC: p95 596ms2026-09-29 UTC: p95 486ms2026-09-30 UTC: p95 519ms2026-10-01 UTC: p95 387ms2026-10-02 UTC: p95 414ms2026-10-03 UTC: p95 458ms2026-10-04 UTC: p95 346ms2026-10-05 UTC: p95 348ms2026-10-06 UTC: p95 309ms2026-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 449ms
Sep 20Oct 4Oct 19
South America
696msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 751ms2026-09-21 UTC: p95 665ms2026-09-22 UTC: p95 982ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 912ms2026-09-26 UTC: p95 984ms2026-09-27 UTC: p95 839ms2026-09-28 UTC: p95 853ms2026-09-29 UTC: p95 777ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 784ms2026-10-02 UTC: p95 868ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 449ms2026-10-06 UTC: p95 708ms2026-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 696ms
Sep 20Oct 4Oct 19

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: 967msstatus code: 200checked: Oct 19, 2026, 9:22 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: 739msstatus code: 200checked: Oct 19, 2026, 9:18 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: 132msstatus code: 200checked: Oct 19, 2026, 9:08 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: 399msstatus code: 200checked: Oct 19, 2026, 9:16 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: 736msstatus code: 200checked: Oct 19, 2026, 9:18 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: 367msstatus code: 200checked: Oct 19, 2026, 9:17 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: 370msstatus code: 200checked: Oct 19, 2026, 9:23 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: 895msstatus code: 200checked: Oct 19, 2026, 9:26 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: 372msstatus code: 200checked: Oct 19, 2026, 9:18 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: 593msstatus code: 200checked: Oct 19, 2026, 9:21 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-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
We have detected an issue., 49mdeclared on their status page2026-09-16
As part of ongoing work to strengthen the resiliency of the Auth0 platform, we are performing a planned DNS change affecting the auth0.com domain, NO customer impact is expected., 165h 16mdeclared on their status page2026-09-02
Elevated Error Rates on Multiple Cloud Environments, 10mdeclared on their status page2026-09-01

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

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>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.