Okta outage history

Okta experienced a partial outage affecting customers using custom domains in the OK9 cell. Beginning at 12:38 PM UTC, users could experience intermittent connectivity when accessing services tied to their custom domains. The impact appeared isolated to custom-domain routing within the Okta Services / Core Platform.

Okta's status updates described the incident as 'Issues with Custom Domains in Cell OK9' with engineering investigating intermittent connectivity errors. The problem persisted through the early window and was recovered by 1:14 PM UTC when the core platform returned to normal operation.

The outage lasted roughly 36 minutes and was localized to the OK9 cell's custom-domain routing, with no indication of a broader, service-wide outage.

Okta experienced an uptick in email deferrals beginning around 2:35 PM UTC, with intermittent email delivery affecting customers in commercial segments. The issue impacted Okta's Core Platform and MFA components, causing some users to miss or delay important messages from Okta, including authentication and notification emails. The Core Identity team began investigating and working to mitigate the issue.

By 4:53 PM UTC the condition had been resolved and Core Platform and MFA returned to normal operation, with services moving back to their standard state.

Okta's core platform experienced a service disruption that caused timeouts and login failures for users on specific cells (OK7/OK14/OK12/OP3). The outage began when the Core Platform moved to down at Jul 24, 2026 12:18 PM UTC and affected sign-in and authentication-dependent services for those cells. The disruption was limited to those cells and did not indicate a full platform-wide outage.

Okta's status page described the event as a Service Disruption with timeouts and login failures, and monitoring showed a return to normal conditions. The Core Platform transitioned back to up by Jul 24, 2026 1:58 PM UTC.

Okta experienced a brief outage affecting Okta Workflows during an extended maintenance window. The disruption impacted workflow automation and integrations relying on Okta Workflows, with users seeing interruptions as the migration overran the original completion time. Impact began at 2:38 PM UTC and persisted until the service came back online later that afternoon.

Okta updated the status to indicate that the Workflows migration would extend beyond the anticipated completion and set a new target completion time of 4:00 PM UTC. The issue was resolved by 4:59 PM UTC, with the Workflows component returning to normal operation.

Okta's Core Platform briefly went offline as part of a quarterly StatusRO disaster recovery (DR) test. The outage began at 1:38 AM UTC and was resolved by 1:43 AM UTC, lasting roughly five minutes. During the window, the Okta Core Platform components were unavailable, which could have temporarily affected authentication and related services for users.

Okta's status update framed the event as a quarterly DR test to ensure tooling and processes are functioning as intended, rather than a production fault. The service was restored promptly, and no ongoing impact was expected beyond the test.

Okta experienced a regional outage in the OP2 cell that disrupted login and access for all users in that region. Users likely encountered connection errors and 5xx responses when signing in or accessing services. The incident began at 8:53 PM UTC as the Core Platform entered a down state for OP2, and Okta stated they were actively investigating and mitigating the issue.

Status updates indicated the problem was isolated to OP2, and service was restored about an hour later, with the OP2 region returning to normal by 9:53 PM UTC. The outage was regional in scope with no reported impact outside OP2, and normal access resumed after remediation.

Impact began around 7:40 PM UTC when Okta’s Workflows team identified an issue affecting customers in US Cell 14, with intermittent issues reported as the front-door gateway for Workflows produced errors. The outage intensified and a formal disruption persisted from 8:23 PM UTC until 9:08 PM UTC, lasting about 1 hour and 30 minutes. Users attempting to trigger or run automation through Okta Workflows experienced failures or delays during this window.

Users attempting to connect to their Okta custom domains encountered connectivity errors, disrupting authentication paths for customers relying on branded, custom domains. The incident began at 3:08 PM UTC and was resolved by 3:38 PM UTC, lasting roughly thirty minutes. Okta Engineering identified a potential cause and began implementing a fix for the Okta Services / Core Platform component responsible for custom-domain connections, with another update expected within 15 minutes. Once the fix was applied, services returned to normal and affected users could sign in and access resources again.

Users in Okta's EU Cell 1 region experienced intermittent login failures and degraded access beginning 9:48 PM UTC. The service reported elevated 500 or 502 errors on its Core Platform, with some users seeing high latency when signing in or accessing apps. Okta investigated and implemented mitigations, with updates as more information became available, affecting authentication workflows for affected customers in that region.

The incident was resolved by 10:33 PM UTC as the Core Platform components returned to normal and service was restored for affected users.

The incident began at Feb 4, 2026 12:33 PM UTC when Okta flagged LDAPi issues in Okta Cell OK9, causing intermittent problems for customers in the EMEA region. The outage affected the LDAPi service and the Okta Core Platform, with users potentially experiencing authentication and directory-related disruptions during the incident.

The outage lasted about 25 minutes and was resolved by Feb 4, 2026 12:58 PM UTC. Okta posted two status updates during the incident, and the regional impact was limited to EMEA Cell OK9 with no wider outages reported.