Is Okta down?

At 6/2/2026 2:45 AM PT, the Core Identity team became aware of an issue with authentication to our service affecting customers in EMEA Cell 9. During this time, users may be experiencing intermittent issues within our system, resulting in error 500. Our team is actively investigating this issue and rerouting the traffic to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. Affected cells: okta.com:9

Engineering is still investigating the issue, recent actions that were taken show errors subsiding.

The Okta Engineering team has observed that the errors have been reduced. We are monitoring the situation closely and will provide further updates as we move toward full mitigation.

Okta Engineering has confirmed that the issue has been resolved. An RCA will be provided in five business days. We apologize for any inconvenience this may have caused.

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 June 2nd, 2026, at 2:36 AM PT, Okta internal monitoring alerted our team to elevated errors in the OK9 environment. During this period, administrators and end users may have experienced intermittent 500 Internal Server errors when trying to access Okta services. Additionally, Admins may have encountered error messages when fetching certain records. Root Cause Summary: The incident was triggered by a misconfiguration introduced during a scheduled maintenance of the environment. This maintenance introduced an error that caused connectivity issues within specific infrastructure components. Only a small percentage of the infrastructure was affected during this period. Remediation Steps: Okta's engineering team identified and isolated impacted infrastructure at 4:01AM PT. These actions successfully addressed the issue, and normal operations were restored by 4:17 AM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: Incident response processes, procedures, and investigation tools to more rapidly diagnose similar issues in the future. Risk evaluation processes to include expanding error types and adding additional appropriate corresponding alerts and monitoring associated with vulnerability updates. These learnings work to prevent similar incidents from happening again and, in cases like these, allow Okta to respond faster when possible. Duration (# of minutes): 100

On April 30, 2026, at 1:07 PM PT, we identified a service disruption when logging on to the OP1 Preview environment. Following the completion of our initial infrastructure rollback, we have confirmed that the underlying service instability persists, indicating a more complex root cause. While our primary focus has been on immediate technical mitigation to stabilize the environment, further analysis reveals that the issue extends beyond the initial proxy configuration. We have now escalated this to our core engineering teams for a comprehensive audit. Emergency routing measures are being evaluated to restore service for critical workflows while we work to isolate and resolve the impact. Affected cells: oktapreview.com:1

The Okta Engineering team has successfully resolved the service instability that was causing system timeouts. Okta engineering has confirmed that errors have subsided, and we have transitioned into a monitoring phase to ensure continued stability. We sincerely appreciate your patience while our team worked to identify and resolve the issue.

Internal monitoring confirmed that the OP1 environment has fully recovered and is operating normally. A full Root Cause Analysis (RCA) will be made available within 5 days. We apologize for any disruption this may have caused.

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 April 30th, 2026, at 10:57 AM PT, Okta internal monitoring alerted our team of login issues for users accessing Okta Preview Cell 1. During this period, customers may have received 500 errors for query timeouts and were unable to log in. Root Cause Summary: The incident stemmed from a database query change. The updated query intermittently exceeded its timeout limit across several login endpoints. Consequently, users experienced 500 errors and were unable to log in. Remediation Steps: Upon receiving the alerts, Okta Engineering immediately launched an investigation. By 1:02 PM PT, the team took initial mitigation steps to resolve the issue, however these steps did not resolve the issue. The incident response team continued to triage and diagnose the issue and identified the root cause related to the updated database query change at 4:50 PM PT. The team reverted the new query behavior at 5:00 PM PT in Preview Cell 1, and full service functionality was restored by 5:05 PM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: -Reviewing incident response processes and investigation tools to more rapidly diagnose similar issues in the future -Risk evaluation processes associated with query updates -Alerts and monitors associated with the database proxy These learnings work to prevent similar incidents from happening again and, in cases like these, allow Okta to respond faster when possible. Duration (# of minutes): 375

On April 22, 2026, at 9:08 AM PT, we confirmed a third-party incident occurred with the Device Trust SAML authentication flow resulting in some users being redirected to an incorrect service provider between approximately 8:24 and 8:30am PT. This behavior originated from Kolide, a third-party middleware integration used for device trust signals and was isolated to organizations that use that specific security layer. While this resulted in users receiving 400 errors and being unable to access their intended applications, our investigation confirms that users were unable to access unauthorized applications or environments. Mitigation was in place by 8:30 AM PT, restoring service. A full root cause analysis will be forthcoming.

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: Customers using the third-party service Kolide began reporting that attempts to sign in to their orgs redirected to an unrelated tenant and received an HTTP 400 error with the message “Login Failed - 400: Bad Request Error Code: GENERAL_NONSUCCESS” Root Cause Summary: Kolide has confirmed for Okta that an incident occurred with their Device Trust SAML authentication system, resulting in some users being redirected to an incorrect service provider after completing authentication. This resulted in users receiving a 400 error. Kolide reported that users were unable to access their intended application, any unauthorized applications, or any unauthorized environments. Remediation Steps: Okta Support advised customers that they could temporarily disable their Kolide integrations to allow their users to successfully access their services. Timing: Kolide reports: Incident start: April 22, 2026, at 8:24 AM PDT Incident resolved: April 22, 2026, at 8:30 AM PDT Duration (# of minutes): 6 Minutes

At 4/13/2026 12:30 PM PT, Engineering became aware of an issue with job processing to our service affecting customers submitting Access Requests. Our team is actively investigating this issue and working on a fix to address the issues. We will provide another update within the next 30 min, or sooner if additional information becomes available.

Okta has identified the issue impacting Access Request job processing and Engineering Teams are working to restore the service. We are rolling out the fix for this issue in 30 minutes and will provide another update once the fix is rolled out.

Okta has identified the root cause of the issue affecting Access Request job processing as of 1:00 PM PT. A resolution was implemented at 1:45 PM PT, and the service is now fully operational for new submissions. The engineering team is currently working to restore and process any requests submitted during the disruption period. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

While new Access Request job processing has been restored, Okta is also working to resolve the issue affecting in-flight Access Request job requests processed during the disruption period.  The fix for this issue is expected to be implemented around 5:00pm PT.  Okta will provide another update at 5:00pm PT or sooner if one becomes available.

The issue with in-flight Access Request job requests processed during the disruption period has also been resolved. All Access Request jobs 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 has 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 kind. Detection and Impact: On April 13, 2026, at 11:51 AM PST, an incident was reported where Okta Identity Governance (OIG) access requests stalled in the "In Progress" state indefinitely across all environments. The system accepted initial submissions and first-level approvals, but failed to trigger subsequent automated tasks like assigning users to apps/groups or running delegated workflows. . Root Cause Summary: During a recent update deployment, new tasks inadvertently moved to a 'LOCKED' status without implementing the necessary logic to transition them back to 'OPEN.' This caused the tasks to become permanently hidden, preventing the automated execution of the action associated with them. Remediation Steps: Okta's engineering teams promptly responded, initiating immediate detection and diagnosis. Corrective measures, including a code fix deployed to all cells, were implemented to prevent any new access requests from becoming stuck. A remediation migration successfully transitioned most affected requests to a fixed state. Normal functionality was fully restored by April 13, 2026, at 5:18 PM PST, following the completion of a final migration to unblock remaining requests.On April 14, 2026, Okta took further steps to resolve in-flight requests that were stuck, moving them to a final, terminal state. Preventative Actions: Okta is taking several steps to prevent this issue from recurring. These include enhanced testing, deployment of safeguards, and improvements to our monitoring and alerting systems. Duration (# of minutes): 434