Okta experienced a major incident on April 30, 2026 affecting Single Sign-On, lasting 7d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 30, 2026, 11:24 PM UTC
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
- monitoring May 01, 2026, 12:28 AM UTC
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.
- resolved May 01, 2026, 01:01 AM UTC
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.
- resolved May 08, 2026, 02:51 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 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