Is Okta down?

At 11/09/2026 05:10 PT, Issues with Custom Domains in Cell OK9 - Customers with custom domains are currently experiencing issues in OK9. Engineering are currently investigating intermittent connectivity errors. Affected cells: okta.com:9

Engineering has identified the issue and taken remediation steps to mitigate the issue. Connectivity to Custom Domains has been restored and the service has returned to normal. Okta will continue to monitor.

Okta has remediated the OK9 connectivity issues. Connectivity errors persisted from 5:00 AM PDT to 5:36 AM PDT. We will continue to monitor and produce an RCA in 5 business days.

At 9/3/2026 2:35 AM PT, the Engineering team became aware of an issue affecting customers in US Preview 1. 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 hour, or sooner if additional information becomes available. Affected cells: oktapreview.com:1

The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

Okta Engineering was able to take the necessary actions to mitigate the issue and is currently monitoring for stability. The cause of the issue and specifics on actions taken will be posted on the Trust page.

After monitoring for an extended period, we confirmed that the issue has not reoccurred. A root cause analysis (RCA) will be posted here within five business days. We sincerely apologize for the impact this had on you and your users.

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 September 2nd, 2026 at 11:43 PM PDT, Okta internal monitoring and customer reports alerted our team of issues for users accessing Okta Preview Cell OP1 in North America. During this period, some customers on OP1 may have experienced HTTP 500 Internal Server Error or 503 Service Unavailable response codes for various endpoints, including those related to authentication and SSO. Root Cause Summary: A release introduced a temporary cache data structure mismatch between software versions. This cache data is used as a part of request evaluation and expected to be forward and backward compatible. As a result, these failed cache object evaluations resulted in errors across core authentication and API endpoints. Remediation Steps: Okta Engineering incident response teams took a number of corrective actions, including rolling back service changes and isolating and clearing incompatible data values from the cache store. Preventative Actions: In order to prevent similar incidents from happening again, Okta has currently implemented the following: Resolved data structure to an upgrade safe implementation Implemented drift detection data consistency enforcement rules and added additional automated tests related to enforcing compatibility between service deployments Additionally, we are reviewing and enhancing our internal testing processes and procedures to prevent this issue from recurring in the future.

At 8/14/2026 7:35 AM PT, the Core Identity team became aware of an issue with email deliverability affecting customers in commercial cells. During this time, users may be experiencing intermittent issues receiving email from Okta. Our team is actively investigating this issue and is working to mitigate it.

Okta Engineering is investigating and has determined that the incident is currently impacting email delivery to a subset of customers. During this time, customers may experience email delivery deferrals. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.

Okta Engineering has determined that certain third-party providers were failing to receive emails from Okta. Our monitoring shows delivery rates are recovering to normal conditions and will continue to monitor until full resolution. Our next update will be in 30 minutes or sooner if additional information becomes available.

Our monitoring indicates that email deferrals to the impacted third-party email service have returned to the expected baseline. Additional information will be available within 5 Business days.

We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Okta detected an increase in customer support tickets regarding email delivery issues. Customers using custom email domains routed through Proofpoint experienced email delivery deferrals. During this period, affected end users were unable to receive system-generated emails, including One-Time Passwords (OTPs), account activation emails, password reset emails, factor enrollment emails, and other automated notifications. Root Cause Summary: Third-party provider Proofpoint experienced a service disruption, causing issues with email deliverability. When Okta services attempted to send emails to recipient domains whose MX records pointed to Proofpoint’s infrastructure, the delivery attempts failed due to connection errors, resulting in deferred delivery. Okta’s email sending infrastructure operated normally throughout the event. Remediation Steps: Okta Engineering monitored service telemetry and confirmed that email delivery returned to normal pre-incident baselines once Proofpoint restored stability to its infrastructure. Preventive Actions: Okta is defining automated alerting thresholds for email-bound and deferral rates to decrease detection time and updating runbooks to allow faster diagnosis of downstream provider disruptions. Timing: Incident start: August 14, 2026, at 5:00 AM PDT Incident resolved: August 14, 2026, at 10:04 AM PDT. Duration (# of minutes): 304 minutes Based on details provided by https://www.proofpoint.com/us/support-services

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.

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. Detection and Impact On July 24, 2026, at approximately 3:55 AM PDT, Okta observed service disruption for US-5 and US-Gov-1 and service degradation for US-7, US-12, US-14, and Preview-3. The incident specifically impacted customers utilizing AD/LDAP delegated authentication and OAuth token-endpoint clients situated within the AWS us-west-2 region. Throughout the event, users encountered errors accessing resources, authentication failures, agent connection timeouts, latency, and OAuth token requests. Root Cause Summary The root cause originated from errors within a cloud service provider for the affected region. Remediation Steps The cloud service provider recovered connectivity, and Okta service stabilized by approximately 4:10 AM PDT, and our teams confirmed a complete return to baseline operations at 4:19 AM PDT. Preventative Actions Okta is actively reviewing and executing several initiatives to prevent future occurrences. These measures include: auditing and improving our incident response processes in the case of extended issues within a region, and refining our monitoring and alerting based on this incident. Total Duration Total Duration (Minutes): 15 minutes Start Time: 3:55 AM PDT End Time: 4:10 AM PDT Duration (# of minutes): 15

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