Okta incident

Import slowness related to third-party provider

Minor Resolved View vendor source →

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

Started
Aug 08, 2025, 09:28 AM UTC
Resolved
Aug 20, 2025, 11:29 PM UTC
Duration
12d 14h
Detected by Pingoru
Aug 08, 2025, 09:28 AM 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 Aug 08, 2025, 09:28 AM UTC

    An issue impacting third party provider(s) regarding import slowness has been resolved. Additional root cause information will be available within 5 business days.

  2. resolved Aug 20, 2025, 11:29 PM UTC

    The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted the Okta service. Timing: Incident start: August 7, at 06:02 PM PDT Incident resolved: August 8, at 02:00PM PT Detection: Okta Engineering was alerted to backend jobs queues increasing due to a slow third-party provider API response. Impact: Customers may have seen slow job processing in Okta. Summary: Jobs were queued due to job execution times increase while waiting for third-party provider API responses. Our third-Party provider has identified a configuration error and resolved this issue by provisioning additional resources to these APIs. Preventive Actions: Okta has introduced additional logging to identify similar disruptions closer to their start.