Is Okta down?

At 3:55 AM PT on July 24th, 2026, the Okta Engineering team became aware of a a third-party incident occurred and affecting customers on OK7/OK14/OK12/OP3 cells of the environment. During this time customers on the impacted cell may experience timeout and not able to login. The issue was resolved at 4:25 AM PT and Okta continues to monitor as our monitoring shows a recovery to normal conditions. Affected cells: okta.com:7, okta.com:12, oktapreview.com:3, okta.com:14

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

Please be advised that our scheduled maintenance is currently still ongoing, and the Okta Engineering teams are actively engaged. During this extended window, customers may experience errors when logging in to Okta Workflows. We appreciate your patience as our teams work to complete this operation as quickly and safely as possible.  To understand how this might impact your organization and to view recommended workarounds, please review our detailed support article: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US . We will provide further updates in 30 minutes, or sooner, as more information becomes available.

Maintenance activity is still ongoing as we ensure the migration is completed safely and successfully.  We will continue to share updates in 30 minutes or sooner, as they become available. In the meantime, please refer to the support article below for the latest guidance on workarounds and expected behaviors: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US

We are now observing stable system performance following the migration activities. Our engineering teams remain actively engaged in monitoring all services. Core workflows are recovering, and customers should see continued improvements. We will provide our next update in 30 minutes, or sooner if new information becomes available.

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

The Workflows migration has extended beyond our anticipated completion and will now be completed at 4:00 PM UTC. We apologize for any inconvenience and will provide further updates as more information becomes available. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11

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 our services to prevent future occurrences. We recognize that this maintenance ran beyond its originally communicated window and that our status updates during that extension did not keep customers informed in a timely way. We apologize for this; improving it is part of our preventative actions below. Detection and Impact On July 22, 2026, at 5:15 AM PDT, Okta Workflows in our North America region (FL1 cell) began experiencing issues that affected Workflows users across US Cells 1, 2, 3, 4, 6, 7, and 11. During this time, some workflow executions failed or ended prematurely, and users encountered errors loading the Workflows Console. Additionally, some app connections stopped working, requiring users to manually reauthenticate to restore functionality. Root Cause Summary The issue occurred during a planned system upgrade. A defect in a third-party vendor's software caused the upgrade to run significantly longer than expected. While migrating to a new datastore system, a communication failure between system components prevented the service from returning to its normal state within the expected window. During this period, the Workflows Console did not degrade gracefully when the underlying data store was unavailable; instead, it surfaced errors directly to users. In addition, app connections whose credentials could not be refreshed during the disruption were left in a failed state and were not automatically refreshed, which is why some errors continued after the upgrade completed, until the affected connection was reauthorized. Remediation Steps The third-party vendor confirmed the cluster stabilized at 8:34 AM PDT. Following stabilization, Okta Engineering recovered affected services to clear stale configuration caches. Any customers who experienced OAuth token refresh errors during this period were required to manually reauthorize any app connections. Full functionality was restored by 9:33 AM PDT. If you’re still affected: manually reauthorize the affected connection credentials in the Workflows Console (see KB: Okta Workflows: Cell Migration Expected Behaviors and Workarounds). Workflow executions that failed during the window can be re-run using your normal process; contact Okta Support if you’d like help identifying affected executions. Preventative Actions To prevent similar incidents from occurring, Okta has taken the following steps. We have enforced a fleet-wide hold on all further datastore engine migrations until our third-party vendor deploys a fix for the confirmed defect and confirms it is safe to proceed. We are also updating the Workflows Console to fail fast and recover automatically when infrastructure is temporarily unavailable, ensuring users see a reconnecting state rather than raw system errors. In parallel, we are adding direct automated monitoring and alerting for cluster-convergence failures to ensure faster detection during maintenance windows. Finally, we are improving how we communicate during maintenance that runs long, including a more timely status page and progress/completion updates. For questions about Workflows reliability or roadmap, your Okta account team can help. Total Duration Total Duration (Minutes): 258 minutes (4 hours and 18 minutes) Start Time: 5:15 AM PDT End Time: 9:33 AM PDT Duration (# of minutes): 258 minutes

This is just a test performed quarterly to ensure the tooling works. Affected cells: OK1

On July 13, 2026, at 1:15 PM PT, we detected a service interruption that impacted all users in cell OP2.  Users may have encountered connection errors or 5xx error messages. Our team is actively investigating this issue and is working to mitigate it. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. Affected cells: oktapreview.com:2

Our engineering team has applied a potential fix to the impacted preview environment and is actively monitoring the system for recovery. We will provide another update within 30 minutes, or sooner if new information becomes available. We sincerely apologize for any inconvenience.

Our Engineering team has applied a fix, and we are observing service restoration to our OP2 preview environment. We are closely monitoring the system and will provide another update within 30 minutes.

We have confirmed that the OP2 preview environment has fully stabilized, and the earlier issue is completely resolved. Additional root cause information will be available within five business days.

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 July 13, 2026 at 1:01 PM PT, Okta internal monitoring alerted our team to elevated errors in the EMEA Preview Cell environment. During this period, all customers in the EMEA Preview Cell environment were impacted, experiencing authentication failures and service slowness. Administrators and end users may have encountered "Internal Server Error" messages and other errors when attempting to sign in or access Okta services. Root Cause Summary: The incident was triggered during a scheduled service upgrade. A misconfiguration caused the EMEA Preview Cell cluster to inadvertently receive an incorrect version of a critical infrastructure routing component. This update broke internal networking routing, which prevented communication between otherwise healthy infrastructure components. Because requests could not reach the core application, it resulted in widespread service errors and authentication failures. Remediation Steps: Okta's engineering team identified the issue and immediately began deploying the previous, stable version of the routing configuration. Following the rollback, engineers systematically restarted the affected services (including gateways and proxies) to restore internal connectivity. These actions successfully addressed the issue, and customer impact was fully mitigated by 2:20 PM PT. Preventative Actions: We are refining our operational processes to enhance service stability. This includes ongoing work to improve auto detection and monitoring capabilities, helping us identify and address potential issues more effectively. Total Duration (Minutes): 79 minutes (1 hour 19 minutes) Start Time: 1:01 PM PT End Time: 2:20 PM PT

At 7/7/2026 12:40 PM PT, the Workflows Automation and Extensibility team became aware of an issue with to our service affecting customers in US Cell 14. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next , or sooner if additional information becomes available. Affected cells: okta.com:14

Okta engineering has an identified an issue affecting Okta Workflows and are currently taking steps to remediate. Customers may see 500 errors or timeouts in the Okta Workflows console, API endpoints, and inbound webhooks. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

The issue with Okta Workflows has been resolved. All Workflows are now processing normally. A root cause analysis (RCA) will be posted here within five business days. We apologize for any inconvenience this may have caused.

We sincerely apologize for any impact this incident may have caused to you, your business, or 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 July 7th, 2026, at 1:01 PM PDT, Okta internal monitoring and customer reports alerted our team to issues with users accessing Workflows on the Okta cell OK14 in North America. During this period, customers on FL14 may have experienced HTTP 500, 503, or 504 Gateway Timeout errors when navigating to Workflows from the admin portal or attempting to log in to the Workflows Console via SSO. Existing sessions may have errored out intermittently. Scheduled and on-demand workflows, inline hooks, and webhooks may have experienced errors and timeouts. Additionally, in-flight executions experienced timeouts. Root Cause Summary: This incident occurred during the planned deployment of release 2027.07.0 to the FL14 cell. In the course of the deployment process, a service pod responsible for executing schema updates was terminated prematurely. This early termination led to unexpected, long-lived database connections, which ultimately caused connection exhaustion on the cell's primary database. Remediation Steps: Upon receiving alerts and customer reports, the team began diagnostics at 12:44 PM PDT. By 1:30 PM PDT, they isolated and removed the service pod performing schema updates. This allowed the database connections to clear, restoring full service by 1:45 PM PDT. Preventative Actions: To prevent future occurrences, Okta is committed to strengthening our infrastructure stability and enhancing our monitoring capabilities. We are currently implementing strategic improvements to our deployment processes and alerting systems to ensure faster detection, response and greater resilience across our services. Total Duration: 67 minutes