Okta outage, 15 November 2024

Issue with requests to US Cell OK6 from a specific geo location

Started
Resolved
15 Nov 2024, 07:34 UTC (after 4 h 32 min)
Impact
Minor
Affected
Core Platform

Is this still happening?

No. Okta marked this incident resolved on 15 Nov 2024, 07:34 UTC, 4 h 32 min after it began.

Right now: Okta reports degraded performance on some systems. (as of 30 Oct, 12:18 UTC) Live Okta status

Last update from Okta

We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact On November 14th, at 6:14 pm PST, Okta was alerted to an issue where requests to US Cell OK6 from a specific geo location may have experienced increased errors and slow response times, and may have received HTTP 503 error messages. Root Cause Summary Based on our investigation and findings, the root cause of this issue was due to a configuration error r...

10 Sept 2025, 19:51 UTC

Read the full incident on the official Okta status page

Similar Okta incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 42 min

    Okta Cell - EU1 has gone into Read Only Mode

  2. , resolved after 36 min

    Issues with Custom Domains in Cell OK9

  3. , resolved after 2 h

    Customer may notice Okta LDAPi issues in Okta Cell OK9.

  4. , resolved after 2 h 16 min

    OK6 Okta Dashboard Access

  5. , resolved after 2 h 16 min

    Issues with Custom Domain in Cell OK7

Other recent Okta incidents

  1. Office 365 Domain Federation Failures

  2. Degraded Performance: Delays in Outbound SMS Delivery

  3. Group Push Delays on OK3

  4. Reporting Unavailable

  5. Group Push failures in EU1

  6. Service Disruption in Workflows

  7. Intermittent Access Issues with Office 365 Apps via Okta

  8. Error 500 observed in OP1

All recorded Okta incidents