Service Disruption in Workflows
On October 01, 2026, at 6:17 AM PT, we're investigating an issue with Okta Workflows where some automated event hook triggers aren't executing as expected. Our engineering team is actively analyzing system logs and working on root-cause remediation. We will provide an update within 30 minutes or as soon as additional information becomes available.
The latest update from Okta.
State
Resolved
Started
31 d ago
2026-10-01 13:17 UTC
Lasted
8 days
until 2026-10-09 03:44 UTC
Worst impact
Partial outage
Timeline
7 updatesUpdate
8 days 100%
Updates
Times in UTCAs posted by Okta
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: On October 1st, 2026, at 6:55 AM PDT, Okta customer reports alerted our team of workflow lag issues for US Cells OK6, OK7, OK8, OK9, and OK11, as well as Okta Preview Cell OP1. During this incident, customers using Okta event hooks experienced delays receiving subscribed events. Workflows triggered by Okta webhooks would have also executed with delays or become non-responsive. In US East Okta Cell 11, a subset of events was dropped entirely, and the webhook delivery failure logs do not appear in the system logs. Root Cause Summary: During our transition to a new internal event delivery system, Okta experienced an issue where retried, consistentl
Following a period of active monitoring, we can confirm that this incident has been fully resolved. Automated event hook execution and queue delivery are operating normally. Additional root cause details will be provided in a formal report within five business days.
We have remediated the root cause affecting automated event hook delivery in Okta Workflows, and the majority of cells have fully recovered. A subset of cells continues to process a backlog of queued events; based on current processing rates, this may take up to 12 hours to complete. We remain in an extended monitoring phase while this backlog clears, and we will provide a further update as the situation progresses.
We have confirmed recovery across several Okta cells, where event hook processing has normalized, and queue backlogs have cleared. Engineering is continuing to track processing metrics across all remaining cells as backlogs normalize. We remain in an extended monitoring phase to ensure sustained system stability across all cells before declaring full resolution. Our next update will be provided in 60 minutes or upon formal closure of the incident.
Okta Workflows performance remains stable, and remaining backlogged events continue to be processed. To ensure sustained system health across all tenants, engineering will maintain active observation. We will share the next update in 60 minutes or as soon as service stabilization is fully confirmed.
System metrics continue to demonstrate sustained recovery following the applied mitigation. New events are being processed successfully, and backlogged events continue to be processed with no recurring errors, consistent with initial customer feedback. We are maintaining active monitoring to ensure ongoing stability. We will provide a final update in 30 minutes or upon formal resolution.
Mitigation steps have been implemented to address delivery and execution delays affecting automated event hook triggers in Okta Workflows. System telemetry indicates that event delivery is recovering and that backlogged automated workflows are beginning to process. We are actively monitoring performance to ensure full stability. A follow-up update will be provided within 15 minutes.
Affected components
1Okta in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
61
Median duration
7 days
This incident
About the median
Other Okta incidents
All incidentsOkta·Office 365 Domain Federation Failures
On October 29, 2026, at 6:45 AM PT, the Okta Engineering Team became aware of an issue with our domain federation management service. Administrators may be unable to add or update domain federations. Existing single sign-on (SSO) and end-user login sessions continue to function normally. Our engineering team is actively monitoring a high-priority vendor support ticket regarding an underlying database replication design change affecting federation management. We will provide another update as soon as additional information becomes available.
Okta·Degraded Performance: Delays in Outbound SMS Delivery
Okta reports delays or failures in outbound SMS delivery, including two-factor authentication codes, on the MFA component. The status is identified. Okta ties the issue to a service disruption at its downstream carrier, China Mobile. Users can use backup methods such as authenticator apps or email.
Okta·Group Push Delays on OK3
On October 21, 2026, at 11:49 AM PT, the Engineering Team became aware of an issue with Group Push affecting our customers in US Cell 3. Impacted customers may experience delays with group push imports. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Okta·Reporting Unavailable
On October 21, 2026, at 11:00 AM PT, Engineering became aware of an issue with our cloud vendor affecting reporting services on EMEA Cell 9. During this time, reporting will not be available. Our team is actively working with our cloud vendor to mitigate the issue. We will provide another update within the next 1 hour, or sooner if additional information becomes available.
Okta·Group Push failures in EU1
At 10/13/2026 6:00 AM PT, the Okta team became aware of an issue with Group Push affecting customer operations in EMEA Cell 1. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Follow Okta
Your coding agent knows when Okta is down, and tells you when a failure is theirs, not yours. You can also get Okta incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "okta" and tell me if Okta has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=okta/feed subscribe https://outages.cc/feed.xml?providers=oktaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane