Okta experienced a minor incident on September 3, 2026 affecting Single Sign-On, lasting 8d 7h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 03, 2026, 09:30 AM UTC
At 9/3/2026 2:35 AM PT, the Engineering team became aware of an issue affecting customers in US Preview 1. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next hour, or sooner if additional information becomes available. Affected cells: oktapreview.com:1
- investigating Sep 03, 2026, 10:42 AM UTC
The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- investigating Sep 03, 2026, 11:02 AM UTC
The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- investigating Sep 03, 2026, 11:34 AM UTC
The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- investigating Sep 03, 2026, 12:00 PM UTC
The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- investigating Sep 03, 2026, 12:30 PM UTC
The Engineering team continues to investigate the error 500 issue in OP1. During this time, users may be experiencing intermittent issues within our system. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- monitoring Sep 03, 2026, 01:03 PM UTC
Okta Engineering was able to take the necessary actions to mitigate the issue and is currently monitoring for stability. The cause of the issue and specifics on actions taken will be posted on the Trust page.
- resolved Sep 03, 2026, 02:09 PM UTC
After monitoring for an extended period, we confirmed that the issue has not reoccurred. A root cause analysis (RCA) will be posted here within five business days. We sincerely apologize for the impact this had on you and your users.
- resolved Sep 11, 2026, 05:26 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 incident. Detection and Impact: On September 2nd, 2026 at 11:43 PM PDT, Okta internal monitoring and customer reports alerted our team of issues for users accessing Okta Preview Cell OP1 in North America. During this period, some customers on OP1 may have experienced HTTP 500 Internal Server Error or 503 Service Unavailable response codes for various endpoints, including those related to authentication and SSO. Root Cause Summary: A release introduced a temporary cache data structure mismatch between software versions. This cache data is used as a part of request evaluation and expected to be forward and backward compatible. As a result, these failed cache object evaluations resulted in errors across core authentication and API endpoints. Remediation Steps: Okta Engineering incident response teams took a number of corrective actions, including rolling back service changes and isolating and clearing incompatible data values from the cache store. Preventative Actions: In order to prevent similar incidents from happening again, Okta has currently implemented the following: Resolved data structure to an upgrade safe implementation Implemented drift detection data consistency enforcement rules and added additional automated tests related to enforcing compatibility between service deployments Additionally, we are reviewing and enhancing our internal testing processes and procedures to prevent this issue from recurring in the future.