Okta outage, 11 June 2025

Service Degradation on Multiple Cells

Started
Resolved
11 Jun 2025, 18:25 UTC (after 12 min)
Impact
Minor
Affected
Core Platform

Is this still happening?

No. Okta marked this incident resolved on 11 Jun 2025, 18:25 UTC, 12 min after it began.

Right now: Okta reports degraded performance on some systems. (as of 30 Oct, 12:16 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 June 11th at 11:04 AM PT, Okta internal monitoring alerted on-call responders regarding a database issue across US Cells 4, 6, 7, 11, and 14. A subset of replica databases in the affected cells were deadlocking, resulting in slow query responses or timeouts. During this time, users and admins may have experienced request slowness and timeout errors....

18 Jun 2025, 22:35 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 18 min

    Service Degradation on Multiple Cells

  2. , resolved after 42 min

    Okta Cell - EU1 has gone into Read Only Mode

  3. , resolved after 36 min

    Issues with Custom Domains in Cell OK9

  4. , resolved after 2 h

    Customer may notice Okta LDAPi issues in Okta Cell OK9.

  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