Okta Outage History

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.

Okta reported intermittent latency and connection issues affecting the OK9 component due to a disruption at a third-party provider. This degraded performance likely impacted authentication and other OK9-dependent operations for some users. The incident began around 3:30 PM UTC and lasted until approximately 7:33 PM UTC, a duration of about 4 hours. The service published two status updates during the event, noting the degradation and later restoration, and guidance to retry failed requests as recovery progressed.

Okta reported an outage affecting some third-party email providers used to deliver verification codes, notifications, and alerts. Users could experience delays or failures in receiving certain emails, though the Okta core platform and customer data remained secure and accessible. The issue was first identified when Okta became aware of the problem at Jan 22, 2026 7:38 PM UTC and the status was raised to a degraded state at Jan 22, 2026 8:48 PM UTC. The incident appears to have been broadly distributed across regions.

Okta reported a disruption in Google Workspace imports that affected admin dashboards, with users seeing errors such as Unexpected Error or Missing Required Field. The issue began around Jan 20, 2026 3:14 PM UTC and the Status page marked the Okta Core Platform as down at Jan 20, 2026 3:43 PM UTC.

The outage lasted about 1 hour 40 minutes, and services were restored by Jan 20, 2026 5:23 PM UTC. The incident involved Okta Services / Core Platform and prompted two official status updates.

The Okta Core Platform experienced degraded performance, affecting users relying on Okta authentication and related services. The outage began at 4:03 PM UTC and was resolved by 7:48 PM UTC.

Okta issued 2 status updates during the incident as teams investigated and then confirmed restoration. The issue appeared isolated to the Okta Services / Core Platform, with no evidence of a broader outage across other Okta services.

The Okta Core Platform experienced a brief degradation beginning at Dec 10, 2025 9:08 AM UTC, with the status moving from up to warn. The outage lasted about 55 minutes and affected authentication and access to apps for some users. The issue was resolved by Dec 10, 2025 10:03 AM UTC. A small volume of user reports described login and access problems during the incident. Okta issued two status updates documenting the degradation and its resolution, reflecting the progression and recovery of the core services.

Okta's Core Platform entered a degraded state beginning at 1:33 PM UTC and was resolved by 5:03 PM UTC. The outage lasted about 3 hours and 30 minutes, during which the platform was listed as degraded. Official updates did not provide detailed notes on which components were affected, and the exact user impact was not described in the communications.

Okta Core Platform experienced a brief degradation affecting authentication and access for users. The incident began at Nov 17, 2025 7:13 PM UTC when the Okta Core Platform component entered a degraded state and was restored by Nov 17, 2025 7:48 PM UTC. The provider issued 2 status updates during the incident describing the degraded condition and the subsequent restoration. The outage lasted about 35 minutes and appeared to have global impact on Okta identity services.

Okta MFA experienced degraded performance, impacting users during multi-factor authentication. The issue was isolated to the Okta MFA component and did not indicate a full service outage in the status updates. Users attempting MFA may have faced intermittent prompts or authentication delays.

Okta API Services experienced a brief degraded performance beginning at 6:43 PM UTC and lasting until 1:48 AM UTC. The Okta Services / API Services component was listed as degraded on the status page during this period, with potential impact to authentication and API-based workflows relied upon by applications. The incident spanned roughly 7 hours and 5 minutes before the status returned to normal.

Okta documented the recovery on the status page as the component transitioned from degraded to up, indicating the issue was resolved by 1:48 AM UTC. The communication reflected the progression from a degraded state to normal operation as status updates were posted.