Okta Outage History

Okta experienced a regional outage in the Core Platform affecting LDAP-related services in Okta Cell OK9, impacting customers in the EMEA region with intermittent authentication and directory access. The outage began on 12:33 PM UTC and was resolved by 12:58 PM UTC, lasting approximately 25 minutes. Okta issued two status updates during the incident as engineers investigated and mitigated the disruption.

Okta experienced intermittent latency and connection issues in OK9 due to a disruption at a third-party provider. Some users faced slower responses and intermittent request failures as retry logic attempted to recover. The incident began at Jan 28, 2026 7:08 PM UTC and was mitigated by Jan 28, 2026 7:33 PM UTC, lasting about 25 minutes. The impact was limited to the Third Party component powering OK9.

The provider issued two status updates during the incident, first acknowledging the latency issue and noting recovery would be gradual, then confirming mitigation and return to normal. User reports were limited during the window.

Okta experienced an incident impacting email delivery for some users, potentially delaying or preventing verification codes, notifications, and alerts. The issue was linked to third-party email service providers and affected the Okta Services / Core Platform, though core authentication and user data remained secure. The outage began at Jan 22, 2026 7:38 PM UTC and was first listed as a degraded service at 8:48 PM UTC. Users reported not receiving emails such as verification codes and 2FA pins. The incident lasted roughly 11 hours, with mail delivery restored by 6:48 AM UTC.

Okta communicated the situation via status updates, acknowledging email delivery issues and confirming ongoing monitoring by their engineering team. Two status updates were issued during the incident, with the service returning to normal by the recovery time 6:48 AM UTC.

Okta's Core Platform experienced a brief disruption affecting Google Workspace imports. Admins may have seen 'Unexpected Error' or 'Missing Required Field' notifications in their dashboards. The outage began on 3:43 PM UTC and was resolved by 5:23 PM UTC, lasting about 1 hour and 40 minutes. Okta issued two status updates during the incident, describing the disruption and later restoration. The issue was isolated to the Google Workspace imports feature within Okta Services / Core Platform, and normal functionality was restored after the incident.

The Okta Core Platform experienced a brief degraded performance starting at Dec 14, 2025 4:03 PM UTC and was restored by Dec 14, 2025 7:48 PM UTC. The incident affected the Okta Services / Core Platform, with the status page listing a degradation and two updates during the event. The outage lasted about 3 hours and 45 minutes.

Okta's Core Platform experienced a short-lived degradation affecting authentication and identity services. User reports began around 8:15 AM UTC, and the official status page showed a degraded state from 9:08 AM UTC. The incident lasted roughly 55 minutes, with restoration completed by 10:03 AM UTC. The impact was limited to the Okta Core Platform.

Okta issued two status updates during the incident: first noting degraded performance at 9:08 AM UTC and later confirming restoration at 10:03 AM UTC. The event appears to have been localized to the Core Platform component.

Okta Services / Core Platform experienced a brief degraded performance starting at Dec 3, 2025 1:33 PM UTC and was restored by Dec 3, 2025 5:03 PM UTC. The incident lasted about 3 hours and 30 minutes. The Okta status page listed the Core Platform in a degraded state and issued two updates during the incident.

Okta Services / Core Platform experienced a brief degradation affecting authentication and related services. The incident began at 7:13 PM UTC and was resolved by 7:48 PM UTC, lasting about 35 minutes. The Status Page indicated the Core Platform moved from up to warn and back to up during the window.

Okta Services / MFA experienced a period of degraded performance starting at Nov 12, 2025 7:48 PM UTC and ending at Nov 14, 2025 1:28 AM UTC. During this time, users attempting to sign in with multi-factor authentication could have faced interruptions or delays, potentially affecting access to apps and services that rely on Okta for authentication. The degraded state lasted for roughly 29 hours and 40 minutes before full recovery.

Okta Services / API Services experienced degraded performance beginning at 6:43 PM UTC and resolving at 1:48 AM UTC, for a total duration of about 7 hours and 5 minutes. During the degraded period, users attempting authentication or API access could have experienced delays or intermittent failures as the affected components operated in a degraded state.

Okta's status page showed the incident transitioning to a degraded state and later returning to normal operation, indicating a temporary disruption across the API surface and authentication flows.