Okta incident

Service Degradation on Multiple Services

Minor Resolved View vendor source →

Okta experienced a minor incident on October 29, 2025 affecting okta-emea.com cell 1 and okta.com cell 1 and 1 more component, lasting 7d. The incident has been resolved; the full update timeline is below.

Started
Oct 29, 2025, 06:40 PM UTC
Resolved
Nov 05, 2025, 06:55 PM UTC
Duration
7d
Detected by Pingoru
Oct 29, 2025, 06:40 PM UTC

Affected components

okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11

Update timeline

  1. resolved Oct 29, 2025, 06:40 PM UTC

    We are aware that some services may be degraded as our third-party vendors are currently experiencing issues. We are actively investigating the scope of the impact and coordinating closely with our providers on a resolution. We will provide an update as soon as more information is available.

  2. resolved Oct 29, 2025, 07:16 PM UTC

    We have confirmed that a third-party provider issue is causing intermittent timeouts when authenticating to the Microsoft O365 portal via Okta Verify. This is impacting a subset of customers. Our provider is actively addressing the issue, and we are closely monitoring their progress on the fix. We will provide the next update in 30 minutes.

  3. resolved Oct 29, 2025, 07:54 PM UTC

    We appreciate your continued patience as we work through this service degradation. Our provider has successfully deployed a fix, and our team is now actively monitoring the environment and performance to confirm full stability. We understand the impact this has on your work, and we are committed to keeping you informed. We will provide our next scheduled status update in 120 minutes, or sooner if we achieve a significant update or confirm a complete fix.

  4. resolved Oct 29, 2025, 11:22 PM UTC

    Remediation work by our third-party provider is ongoing, and Okta is observing consistent recovery across affected cells. Our next scheduled update is within 90 minutes or earlier if additional information becomes available.

  5. resolved Oct 30, 2025, 01:47 AM UTC

    After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved by our third-party provider. Additional root cause information will be available within five business days.

  6. resolved Nov 05, 2025, 06:54 PM UTC

    Timing: Incident start: October 29, 2025, at 7:15 AM PDT Incident resolved: October 29, 2025, at 4:05 PM PDT Detection: Okta monitoring detected errors when redirecting to Microsoft. Concurrently, customers began reporting intermittent timeouts when authenticating to Microsoft services and when using Okta Verify. Impact: A subset of customers experienced intermittent timeouts and SSO login failures when authenticating to Microsoft services (such as Microsoft 365). Further, customers may have seen timeouts in Azure webhooks and other redirects to Microsoft services. Root Cause: Microsoft Azure experienced connectivity issues with its Azure Front Door service across multiple regions. This resulted in latency, timeouts, and errors for client redirection, causing intermittent timeouts and authentication failures for Okta users attempting to authenticate to Microsoft services. Microsoft provides additional details for this disruption under tracking ID: YKYN-BWZ: https://azure.status.microsoft/en-us/status/history/ Remediation Steps: Okta monitored the disruption while Microsoft worked on a resolution. Okta monitoring showed error rates began to decrease at 11:35 AM PDT, and Microsoft confirmed that their services were fully restored at 4:05 PM PDT.