Okta experienced a minor incident on October 20, 2025 affecting okta.com cell 1 and okta.com cell 2 and 1 more component, lasting 35d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Oct 20, 2025, 06:48 AM UTC
At 20/10/2025 00:15 PT, We're currently experiencing technical difficulties for workflows that are related to an issue with an upstream provider. We're working with the vendor and will provide updates in the next 30 minutes
- resolved Oct 20, 2025, 08:44 AM UTC
We're currently experiencing service degradation throughout Workflows across all cells. Due to an issue with an upstream provider, Cells OK1 to OK4 and OP1 are currently impacted. We're working with the vendor and will provide updates in the next 30 minutes.
- resolved Oct 20, 2025, 09:22 AM UTC
Okta engineers have made service changes to Workflows to mitigate the issues. Flow executions continue to improve. There are other issues that we are still investigating and will attempt to mitigate further for OK1 to OK4 and OP1. We're working with the vendor and will provide updates in the next 30 minutes
- resolved Oct 20, 2025, 09:42 AM UTC
We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes
- resolved Oct 20, 2025, 10:13 AM UTC
We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes
- resolved Oct 20, 2025, 10:44 AM UTC
We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows processing has been restored across all Cells. Customers should review their flow executions during the outage as they may have to rerun flows that failed during that time. We will provide updates in the next 60 minutes.
- resolved Oct 20, 2025, 11:51 AM UTC
We are still seeing significant improvements in our services in Cells OK1 through to OK4 and OP1. Customers may still experience issues with viewing Syslog events in OK1. We will provide updates in the next 60 minutes.
- resolved Oct 20, 2025, 12:48 PM UTC
We are continuing to monitor improvements in our services in Cells OK1 through to OK4 and OP1. Customers may still experience issues with viewing Syslog events in OK1. We will provide an update at approximately 9:30 AM PDT.
- resolved Oct 20, 2025, 04:41 PM UTC
We are maintaining our focused monitoring effort on Cells OK1 through to OK4 and OP1. Workflows services have recovered in all US Cells and we recommend reviewing existing workflows for consistency around third-party interactions. We are aware that the experience for viewing Syslog events in OK1 has not yet resolved and we are continuing to remediate these issues. We will provide updates in the next 60 minutes.
- resolved Oct 20, 2025, 06:14 PM UTC
We are actively working on persisting issues with Syslog delays in OK1. We will provide our next status updates in 120 minutes or earlier as soon as information becomes available.
- resolved Oct 20, 2025, 07:00 PM UTC
We are seeing sustained recovery and improved processing speeds in Cell OK1 on Syslog events. which is helping to work through the existing backlog. We’re continuing to monitor the situation closely to ensure this improvement is sustained. We will provide next update in 180 minutes, or sooner if the backlog is fully processed.
- resolved Oct 20, 2025, 09:09 PM UTC
Stability in Cell OK1 continues to show consistent improvement. We are still processing the remaining system logs and will provide our next update in 120 minutes.
- resolved Oct 20, 2025, 11:17 PM UTC
Okta continues to mitigate and resolve event processing delays in OK1. We have deployed additional resources to improve processing of events to reduce these delays. We are observing improved processing times and will continue to monitor and will update in 120 minutes.
- resolved Oct 21, 2025, 01:00 AM UTC
Following the deployment of additional capacity and resources, we've seen steady acceleration in processing rates. We will continue to track this progress and provide another update in the next 120 minutes.
- resolved Oct 21, 2025, 02:19 AM UTC
The issue impacting Syslog processing delays in OK1 and the previous Workflow issues have been resolved and the services have been restored. Additional root cause information will be available within 5 business days.
- resolved Oct 29, 2025, 12:10 AM UTC
We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: Okta’s cloud service provider reported errors starting at 11:48 PM PT per their post-incident assessment. Below is the Okta timeline for the impact on our services. Okta Workflows: On October 19th at 11:55 PM PT Okta began receiving alerts regarding Workflows issues occurring in US FL1. During the incident, customers in this cell experienced errors accessing the Workflows UI. Most workflows continued executing normally during this incident, except for those that contained Workflows Table cards, which included create, update, import, or export functionality. Due to latency issues, organizations invoking API endpoint flows encountered timeouts waiting for flows to complete. Actual Impact Time: Sunday 11:55 PM PT - Monday 2:02 AM PT Okta Syslog Event Processing/Log Streaming Delays: On October 20th at 12:23 AM PT, Okta began receiving alerts that systems related to our system log processing were experiencing delays and errors. Okta immediately began to investigate the issue. During the incident, customers in OK1, OK2, OK3, and OK4 experienced delays in event logs and reports. Additionally, the incident impacted Stream and Webhook events, resulting in increased event processing times. OK2, OK3, OK4 Actual Impact Time: Sunday 11:48 PM PT - Monday 3:36 AM PT OK1 Actual Impact Time: Sunday 11:48 PM PT - Monday 6:46 PM PT Okta SMS MFA Processing errors: Some customers may have also seen SMS delivery and retry failures due to errors in downstream third-party telephony providers. Users were able to access the UI and Admins, and were able to log in. Actual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT Actual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT Root Cause Summary: Okta’s cloud service provider experienced system issues that impacted the Okta service. Remediation Steps: Okta Workflows: After reviewing internal alerting and investigating the issue, at 2:02 AM PT, Okta took mitigating actions to bypass the impacted cloud provider services, and Workflows began stabilizing. Okta continued to monitor until approximately 11:49 AM PT by which time functionality had normalized. Okta Syslog Event Processing/Log Streaming Delays: Following a review of internal alerts, Okta began to analyze and address impacted services. At 2:12 AM PT, OK2, OK3, and OK4 were restored to full operation, and Okta Engineering verified the appropriate resolution of the incident. Events began processing and fully recovered in these environments at 3:36 AM PT. While all other cells had recovered, OK1 continued to experience longer system event processing delays. Once the cloud service system was stabilized, Okta was able to scale up the processing. All system log events for OK1 events were processed by 6:46 PM PT. Preventative Actions: Okta is working closely with the cloud service provider to investigate additional mitigations and improve response to these types of incidents. In addition, Okta is looking for opportunities to improve processes to identify and mitigate issues related to cloud service provider issues faster and more efficiently.