Okta experienced a degradation tied to a third-party component, causing a temporary impact on services relying on that dependency. The Third Party component was listed as degraded on Okta's status page, with no other Okta components affected.
Okta reported a brief degradation across three OIG components: OIG Reporting, OIG Access Certifications, and OIG Access Requests. The incident began at and caused degraded performance for users relying on these features.
By , OIG Reporting and OIG Access Certifications had returned to normal, while OIG Access Requests remained degraded. The final component recovered by , bringing the total duration to about two hours. The provider issued 3 status updates during the incident.
Minor
: Okta Workflows briefly degraded, then recovered
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(25 minutes)
Okta experienced a brief degradation in the Okta Services / Workflows component, potentially affecting automated workflows for a short period. The incident began at when the component was listed as degraded and was resolved by , lasting about 25 minutes. The Okta status page documented the issue with 2 official updates during the event, and the recovery followed shortly after. No root cause details were provided in the updates.
Minor
: Okta Core Platform brief degradation, recovered in 20 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(20 minutes)
Okta Services / Core Platform experienced a brief degraded state beginning at , as the status page moved to a warning. The Core Platform component was affected and users may have encountered intermittent issues, though no user-reported impact was observed. The incident lasted approximately 20 minutes and was resolved by . The provider issued two status updates during the event describing the degraded condition and its resolution.
Looking for more Okta outage stats?
Get real-time insights and historical data on Okta outages.