Okta experienced a major incident on January 9, 2025 affecting Advanced Server Access, lasting 45d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jan 09, 2025, 07:32 PM UTC
On 1/9/2025 10:42 AM PT, the Advanced Server Access team became aware of an issue with our Advanced Server Access service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, US Cell 7, US Cell 8, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, Preview Cell 1, Preview Cell 2, and Preview Cell 3. During this time, administrators were unable to access the ASA dashboard. This issue has since been resolved. Root cause information: 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 January 9, 2025 starting at approximately 10:42AM PT, Okta was alerted to an issue where Advanced Server Access (ASA) customers were unable to access the ASA UI console. All ASA UI actions were unavailable, including logins and administrative actions within the console. Any ASA actions via client API were unimpacted. Root Cause Summary: Okta’s Engineering team determined the root cause of the issue was a recent update to the ASA dashboard which referenced a missing JavaScript asset. This resulted in all ASA UI access being temporarily unavailable. This did not impact client API access, server registration or other ASA resource actions. Remediation Steps & Preventative Actions: Okta identified the issue at 11:10AM PT and Okta engineering deployed the solution at 11:19AM PT, reverting to an earlier version and restoring access. Okta is adding additional automated test scenarios to prevent similar incidents from happening in the future. We will increase monitoring and implement additional sign-off during future service updates. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, okta.com:15, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17
- resolved Jan 16, 2025, 02:42 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 January 9, 2025 starting at approximately 10:42AM PT, Okta was alerted to an issue where Advanced Server Access (ASA) customers were unable to access the ASA UI console. All ASA UI actions were unavailable, including logins and administrative actions within the console. Any ASA actions via client API were unimpacted. Root Cause Summary: Okta’s Engineering team determined the root cause of the issue was a recent update to the ASA dashboard which referenced a missing JavaScript asset. This resulted in all ASA UI access being temporarily unavailable. This did not impact client API access, server registration or other ASA resource actions. Remediation Steps & Preventative Actions: Okta identified the issue at 11:10AM PT and Okta engineering deployed the solution at 11:19AM PT, reverting to an earlier version and restoring access. Okta is adding additional automated test scenarios to prevent similar incidents from happening in the future. We will increase monitoring and implement additional sign-off during future service updates.