Okta Outage History

The outage began on Oct 20, 2025 9:07 AM UTC when Okta Services / Workflows entered a degraded state. A follow-up update at 9:56 AM UTC indicated Third Party integrations were also degraded, while Okta Services / Workflows recovered to an active state. The Third Party component remained degraded until Oct 21, 2025 2:18 AM UTC when it returned to up. The overall incident lasted about 17 hours.

The outage began at 6:38 PM UTC with Okta Core Platform entering a degraded state, affecting core functionality for some users. A subsequent status update at 6:43 PM UTC showed the Okta Core Platform returning to normal, while a related third-party component briefly entered a degraded state. All services were fully restored by 7:23 PM UTC. The incident lasted about 45 minutes and involved two components, with Okta issuing three status updates during the event.

Okta Core Platform experienced a brief period of degraded performance affecting authentication and access for some users. The incident began at 11:58 PM UTC and was resolved by 12:33 AM UTC, lasting about 35 minutes. Okta's status page indicated a degraded condition on the Core Platform and then returned to full operation. The provider issued 2 status updates during the incident, communicating the degraded state and the subsequent restoration.

Okta Services / Workflows experienced a prolonged degraded performance starting on Oct 1, 2025 9:33 PM UTC and was resolved by Oct 9, 2025 10:58 PM UTC. This impacted automation tasks and workflows dependent on Okta Workflows, potentially causing delays or failures in identity-related processes. The service issued two status updates during the incident to communicate the ongoing issue and eventual recovery. User reports were sparse, with at least one observation from Loveland, Ohio.

Okta Services / Workflows experienced a brief degraded performance beginning at Sep 22, 2025 12:33 PM UTC and returning to normal by Sep 22, 2025 10:28 PM UTC. The degraded period lasted about 9 hours and 55 minutes and affected workflow automation and integration features within Okta.

The Okta status page showed the component moving from a degraded state to healthy, with 2 official status updates issued during the incident as the platform teams investigated and confirmed recovery.

On Aug 18, 2025 3:18 PM UTC the Okta Core Platform entered a degraded state affecting core identity and authentication services. The degradation continued until Aug 18, 2025 6:38 PM UTC, for a total duration of approximately 3 hours and 20 minutes. Okta published two status updates during the incident and noted limited user reports with no clear regional pattern identified, before services returned to normal.

Okta Services / Workflows experienced a degraded period beginning on Aug 1, 2025 3:38 PM UTC and ending on Aug 2, 2025 3:58 AM UTC, lasting about 12 hours and 20 minutes. During this window, users may have encountered delays or intermittent failures when automating workflows through Okta. The Okta status page showed a transition from normal to degraded (warn) and back to normal as the issue resolved.

Okta Core Platform experienced a brief degradation from 6:48 PM UTC to 8:38 PM UTC on 2025-07-22, with services returning to normal after approximately 1 hour and 50 minutes. Okta published two status updates during the incident, confirming ongoing remediation and eventual restoration. The outage affected the Okta Services / Core Platform.

Okta experienced brief degraded performance affecting the Third Party integration, with some users reporting slower responses when interacting with external services tied to Okta. The issue appeared limited to this component and did not indicate a full service outage.

The incident began at 6:44 PM UTC and was resolved by 8:08 PM UTC, lasting about 1 hour 24 minutes. The provider updated the status page twice during the incident, changing the component status from up to warn and back to up.

Okta Services / Core Platform experienced a brief degraded period from Jun 11, 2025 7:18 PM UTC to Jun 11, 2025 7:33 PM UTC (about 15 minutes). The incident did not indicate widespread user impact, and no user reports were observed. The provider issued two status updates during the event, first noting degraded performance and then confirming restoration as service returned to normal.