Skip to content

Outage tracker / Okta

Is Okta down?

I'm having a problem

Vendor reports no incidentWhat Okta reports

Okta reports no incident on its status page.

As of the last successful poll, 2026-10-23 11:47 UTC.

Okta'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 Okta pass from all 10 regions we check.

As of Oct 23, 2026, 11:57 AM UTC, RealUptime's checks of Okta passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 11:57 AM UTC
US-East280 msChecks passing
US-West874 msChecks passing
Europe575 msChecks passing
Asia-Pacific1043 msChecks passing
US-Central188 msChecks passing
Canada189 msChecks passing
UK58 msChecks passing
Southeast Asia692 msChecks passing
Australia281 msChecks passing
South America265 msChecks passing
their status pagetheir claim, not our reading

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

Okta response time, by region

US-East
420msp95 · 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-24 UTC: p95 660ms2026-09-25 UTC: p95 639ms2026-09-26 UTC: p95 614ms2026-09-27 UTC: p95 549ms2026-09-28 UTC: p95 544ms2026-09-29 UTC: p95 611ms2026-09-30 UTC: p95 560ms2026-10-01 UTC: p95 525ms2026-10-02 UTC: p95 337ms2026-10-03 UTC: p95 356ms2026-10-04 UTC: p95 348ms2026-10-05 UTC: p95 331ms2026-10-06 UTC: p95 308ms2026-10-07 UTC: p95 354ms2026-10-08 UTC: p95 405ms2026-10-09 UTC: p95 418ms2026-10-10 UTC: p95 386ms2026-10-11 UTC: p95 387ms2026-10-12 UTC: p95 323ms2026-10-13 UTC: p95 463ms2026-10-14 UTC: p95 505ms2026-10-15 UTC: p95 514ms2026-10-16 UTC: p95 559ms2026-10-17 UTC: p95 895ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 441ms2026-10-23 UTC: p95 420ms
Sep 24Oct 8Oct 23
US-West
1.1sp95 · 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-24 UTC: p95 505ms2026-09-25 UTC: p95 476ms2026-09-26 UTC: p95 461ms2026-09-27 UTC: p95 346ms2026-09-28 UTC: p95 364ms2026-09-29 UTC: p95 369ms2026-09-30 UTC: p95 352ms2026-10-01 UTC: p95 374ms2026-10-02 UTC: p95 350ms2026-10-03 UTC: p95 416ms2026-10-04 UTC: p95 334ms2026-10-05 UTC: p95 352ms2026-10-06 UTC: p95 313ms2026-10-07 UTC: p95 338ms2026-10-08 UTC: p95 334ms2026-10-09 UTC: p95 402ms2026-10-10 UTC: p95 332ms2026-10-11 UTC: p95 371ms2026-10-12 UTC: p95 333ms2026-10-13 UTC: p95 387ms2026-10-14 UTC: p95 379ms2026-10-15 UTC: p95 320ms2026-10-16 UTC: p95 324ms2026-10-17 UTC: p95 841ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 986ms2026-10-21 UTC: p95 942ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Europe
824msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 390ms2026-09-25 UTC: p95 329ms2026-09-26 UTC: p95 387ms2026-09-27 UTC: p95 410ms2026-09-28 UTC: p95 399ms2026-09-29 UTC: p95 311ms2026-09-30 UTC: p95 414ms2026-10-01 UTC: p95 441ms2026-10-02 UTC: p95 374ms2026-10-03 UTC: p95 367ms2026-10-04 UTC: p95 349ms2026-10-05 UTC: p95 384ms2026-10-06 UTC: p95 363ms2026-10-07 UTC: p95 381ms2026-10-08 UTC: p95 329ms2026-10-09 UTC: p95 286ms2026-10-10 UTC: p95 327ms2026-10-11 UTC: p95 339ms2026-10-12 UTC: p95 385ms2026-10-13 UTC: p95 200ms2026-10-14 UTC: p95 473ms2026-10-15 UTC: p95 259ms2026-10-16 UTC: p95 273ms2026-10-17 UTC: p95 563ms2026-10-18 UTC: p95 743ms2026-10-19 UTC: p95 935ms2026-10-20 UTC: p95 634ms2026-10-21 UTC: p95 443ms2026-10-22 UTC: p95 884ms2026-10-23 UTC: p95 824ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.4sp95 · 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-24 UTC: p95 637ms2026-09-25 UTC: p95 568ms2026-09-26 UTC: p95 686ms2026-09-27 UTC: p95 840ms2026-09-28 UTC: p95 600ms2026-09-29 UTC: p95 557ms2026-09-30 UTC: p95 521ms2026-10-01 UTC: p95 556ms2026-10-02 UTC: p95 611ms2026-10-03 UTC: p95 576ms2026-10-04 UTC: p95 792ms2026-10-05 UTC: p95 609ms2026-10-06 UTC: p95 511ms2026-10-07 UTC: p95 424ms2026-10-08 UTC: p95 468ms2026-10-09 UTC: p95 497ms2026-10-10 UTC: p95 523ms2026-10-11 UTC: p95 519ms2026-10-12 UTC: p95 470ms2026-10-13 UTC: p95 506ms2026-10-14 UTC: p95 618ms2026-10-15 UTC: p95 657ms2026-10-16 UTC: p95 857ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s
Sep 24Oct 8Oct 23
US-Central
600msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 552ms2026-09-25 UTC: p95 458ms2026-09-26 UTC: p95 625ms2026-09-27 UTC: p95 669ms2026-09-28 UTC: p95 599ms2026-09-29 UTC: p95 479ms2026-09-30 UTC: p95 520ms2026-10-01 UTC: p95 457ms2026-10-02 UTC: p95 549ms2026-10-03 UTC: p95 533ms2026-10-04 UTC: p95 499ms2026-10-05 UTC: p95 498ms2026-10-06 UTC: p95 576ms2026-10-07 UTC: p95 552ms2026-10-08 UTC: p95 547ms2026-10-09 UTC: p95 576ms2026-10-10 UTC: p95 494ms2026-10-11 UTC: p95 546ms2026-10-12 UTC: p95 554ms2026-10-13 UTC: p95 518ms2026-10-14 UTC: p95 321ms2026-10-15 UTC: p95 308ms2026-10-16 UTC: p95 504ms2026-10-17 UTC: p95 745ms2026-10-18 UTC: p95 946ms2026-10-19 UTC: p95 970ms2026-10-20 UTC: p95 883ms2026-10-21 UTC: p95 901ms2026-10-22 UTC: p95 516ms2026-10-23 UTC: p95 600ms
Sep 24Oct 8Oct 23
Canada
681msp95 · 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-24 UTC: p95 629ms2026-09-25 UTC: p95 603ms2026-09-26 UTC: p95 459ms2026-09-27 UTC: p95 351ms2026-09-28 UTC: p95 395ms2026-09-29 UTC: p95 438ms2026-09-30 UTC: p95 504ms2026-10-01 UTC: p95 535ms2026-10-02 UTC: p95 462ms2026-10-03 UTC: p95 497ms2026-10-04 UTC: p95 567ms2026-10-05 UTC: p95 445ms2026-10-06 UTC: p95 459ms2026-10-07 UTC: p95 465ms2026-10-08 UTC: p95 478ms2026-10-09 UTC: p95 516ms2026-10-10 UTC: p95 439ms2026-10-11 UTC: p95 367ms2026-10-12 UTC: p95 393ms2026-10-13 UTC: p95 405ms2026-10-14 UTC: p95 427ms2026-10-15 UTC: p95 412ms2026-10-16 UTC: p95 506ms2026-10-17 UTC: p95 963ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 509ms2026-10-23 UTC: p95 681ms
Sep 24Oct 8Oct 23
UK
203msp95 · 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-24 UTC: p95 302ms2026-09-25 UTC: p95 278ms2026-09-26 UTC: p95 285ms2026-09-27 UTC: p95 190ms2026-09-28 UTC: p95 190ms2026-09-29 UTC: p95 322ms2026-09-30 UTC: p95 227ms2026-10-01 UTC: p95 467ms2026-10-02 UTC: p95 307ms2026-10-03 UTC: p95 338ms2026-10-04 UTC: p95 335ms2026-10-05 UTC: p95 384ms2026-10-06 UTC: p95 402ms2026-10-07 UTC: p95 307ms2026-10-08 UTC: p95 299ms2026-10-09 UTC: p95 564ms2026-10-10 UTC: p95 213ms2026-10-11 UTC: p95 269ms2026-10-12 UTC: p95 209ms2026-10-13 UTC: p95 244ms2026-10-14 UTC: p95 184ms2026-10-15 UTC: p95 194ms2026-10-16 UTC: p95 210ms2026-10-17 UTC: p95 569ms2026-10-18 UTC: p95 693ms2026-10-19 UTC: p95 859ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 347ms2026-10-22 UTC: p95 305ms2026-10-23 UTC: p95 203ms
Sep 24Oct 8Oct 23
Southeast Asia
1.3sp95 · 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-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 967ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 890ms2026-10-10 UTC: p95 671ms2026-10-11 UTC: p95 637ms2026-10-12 UTC: p95 572ms2026-10-13 UTC: p95 487ms2026-10-14 UTC: p95 546ms2026-10-15 UTC: p95 564ms2026-10-16 UTC: p95 588ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
Australia
533msp95 · 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-09-24 UTC: p95 713ms2026-09-25 UTC: p95 751ms2026-09-26 UTC: p95 917ms2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 901ms2026-10-05 UTC: p95 896ms2026-10-06 UTC: p95 929ms2026-10-07 UTC: p95 867ms2026-10-08 UTC: p95 829ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 775ms2026-10-15 UTC: p95 794ms2026-10-16 UTC: p95 871ms2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 663ms2026-10-23 UTC: p95 533ms
Sep 24Oct 8Oct 23
South America
580msp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 927ms2026-09-25 UTC: p95 916ms2026-09-26 UTC: p95 938ms2026-09-27 UTC: p95 872ms2026-09-28 UTC: p95 989ms2026-09-29 UTC: p95 945ms2026-09-30 UTC: p95 816ms2026-10-01 UTC: p95 851ms2026-10-02 UTC: p95 783ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 940ms2026-10-06 UTC: p95 761ms2026-10-07 UTC: p95 894ms2026-10-08 UTC: p95 900ms2026-10-09 UTC: p95 855ms2026-10-10 UTC: p95 809ms2026-10-11 UTC: p95 805ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 990ms2026-10-14 UTC: p95 743ms2026-10-15 UTC: p95 624ms2026-10-16 UTC: p95 816ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 946ms2026-10-23 UTC: p95 580ms
Sep 24Oct 8Oct 23

Check your own site while you wait on Okta

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

What we measured, function by function

Okta 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 Okta reports an incident on its status page, and again when it reports it resolved.

Get an email when Okta reports an incident

Email me when Okta 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 Okta'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: 280msstatus code: 200checked: Oct 23, 2026, 11:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Okta normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 874msstatus code: 200checked: Oct 23, 2026, 11:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Okta normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 188msstatus code: 200checked: Oct 23, 2026, 11:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Okta normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 189msstatus code: 200checked: Oct 23, 2026, 11:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Okta normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 265msstatus code: 200checked: Oct 23, 2026, 11:56 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Okta 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: 575msstatus code: 200checked: Oct 23, 2026, 11:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Okta normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 58msstatus code: 200checked: Oct 23, 2026, 11:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Okta 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: 1043msstatus code: 200checked: Oct 23, 2026, 11:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Okta normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 692msstatus code: 200checked: Oct 23, 2026, 11:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Okta normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 281msstatus code: 200checked: Oct 23, 2026, 11:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Okta 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 Okta, 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 Okta yet, which is not evidence that nothing is wrong.

Recent probe events

Group Push Delays on OK3, 1h 15mdeclared on their status page2026-10-21
Reporting Unavailable, 1h 8mdeclared on their status page2026-10-21
Group Push failures in EU1, 1h 20mdeclared on their status page2026-10-13
Okta Cell - EU1 has gone into Read Only Mode, 42mdeclared on their status page2026-10-13
Service Disruption in Workflows, 10h 43mdeclared on their status page2026-10-01
Intermittent Access Issues with Office 365 Apps via Okta, 82h 57mdeclared on their status page2026-09-15
Issues with Custom Domains in Cell OK9, 36mdeclared on their status page2026-09-11
Error 500 observed in OP1, 4h 39mdeclared on their status page2026-09-03

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

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

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

Okta uptime by RealUptime's checksLive, from this page's own readings.
[![Okta uptime by RealUptime's checks](https://realuptime.io/outages/okta/badge.svg?days=30)](https://realuptime.io/outages/okta)
<a href="https://realuptime.io/outages/okta"><img src="https://realuptime.io/outages/okta/badge.svg?days=30" alt="Okta 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 Okta down?", https://realuptime.io/outages/okta. 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://login.okta.com/.well-known/openid-configuration
secondary
https://status.okta.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: login.okta.com

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