Okta outage, 4 February 2026

Customer may notice Okta LDAPi issues in Okta Cell OK9.

Started
Resolved
4 Feb 2026, 12:41 UTC (after 2 h)
Impact
Major
Affected
Core Platform

Is this still happening?

No. Okta marked this incident resolved on 4 Feb 2026, 12:41 UTC, 2 h after it began.

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

Last update from Okta

On February 4th, 2026, at 3:33 AM PT, Okta received customer reports of authentication failures within the OK9 (EMEA) cell. Customers attempting to access LDAP interface services encountered certificate validation errors related to hostname mismatches, preventing successful authentication. Root Cause Summary: The incident was triggered by a misconfiguration introduced during a scheduled update of our LDAP interface to a new configuration source on February 4th 2:24 AM PT. This update inadvertently applied an incorrect SSL certificate profile to the LDAP interface within the OK9 environment. This misconfiguration caused certificate validity errors, resulting in connection issues when attempti...

11 Feb 2026, 18:45 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 36 min

    Issues with Custom Domains in Cell OK9

  2. , resolved after 42 min

    Okta Cell - EU1 has gone into Read Only Mode

  3. , resolved after 2 h 16 min

    Issues with Custom Domain in Cell OK7

  4. , resolved after 42 min

    Issues with Custom Domain in Cell OK7

  5. , resolved after 18 min

    Service Degradation on Multiple Cells

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