Issues with delauth authentication resulting in error 500

Update timeline

1. investigating Jun 02, 2026, 12:45 AM UTC

   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

2. investigating Jun 02, 2026, 11:21 AM UTC

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

3. monitoring Jun 02, 2026, 11:40 AM UTC

   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.

4. resolved Jun 02, 2026, 12:07 PM UTC

   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.

5. resolved Jun 10, 2026, 02:19 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: 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