Okta experienced a critical incident on December 11, 2024 affecting okta-emea.com cell 1 and okta.com cell 1 and 1 more component, lasting 273d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Dec 11, 2024, 06:32 PM UTC
Okta is currently experiencing an issue with end-user and admin logins. We are actively investigating and will update this message with more information as soon as we have it.
- resolved Dec 11, 2024, 07:41 PM UTC
Okta's Engineering Team has identified an issue affecting end-user and admin login and has taken remediation steps on affected cells. We are currently seeing an improvement in login success rates and will continue to monitor for full recovery.
- resolved Dec 11, 2024, 07:50 PM UTC
The login issue for all impacted Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor for any further errors. Additional root cause information will be available within 5 Business days.
- resolved Dec 18, 2024, 11:59 PM 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 kind of incident. Detection and Impact: On December 11th at 10:42AM PT, Okta internal monitoring alerted on-call responders regarding an issue across cells OK1 and EU1, and later on, limited impact in OK5, OK8, and OK16. During this time, some users were unable to load the Okta Sign In Widget, preventing authentication actions. Some admins were unable to open support cases unless they had an active session within the Okta Help Center. Existing sessions for end users and admins continued to operate normally. All other Okta products and services continued to function as designed. Root Cause Summary: The Okta engineering team was attempting to preemptively mitigate an identified risk in an upcoming version. While the change followed all processes for such changes, it was applied incorrectly ahead of the deployment causing the login page to reference an unavailable version of the Okta Sign in Widget in impacted production cells. For per-environment timelines, please review the specific timelines below. Timelines: OK1 10:32AM - 11:08AM PT 36 minutes [SIW Gen2] OK1 10:32AM - 11:15AM PT 43 minutes [SIW Gen3] EU1 10:40AM - 11:15AM PT 35 minutes [SIW Gen2] EU1 10:40AM - 11:18AM PT 38 minutes [SIW Gen3] OK8 11:01AM - 11:25AM PT 24 minutes [SIW Gen 2] OK8 11:01AM - 11:30AM PT 29 minutes [SIW Gen 3] OK16 10:59AM - 11:23AM PT 24 minutes [SIW Gen 2] OK5 10:47AM - 11:47AM PT 60 minutes [SIW Gen 2] Remediation Steps: Upon receiving automated alerts and support cases, Okta began diagnosing the incident and discovered the root cause at 10:58AM PT. At that time, the team started incrementally remediating the issue. The team rolled back the change across all impacted environments by 11:47AM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta has immediately addressed the following: Updated controls and enhanced approval flows for configuration changes Enhanced monitoring and alerting for content load errors for faster detection and response Duration (Minutes): 78