# Okta: Error 500 observed in OP1

- Provider: [Okta](https://outages.cc/okta.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-09-03 09:30 UTC
- Resolved: 2026-09-11 17:26 UTC (lasted 8 days)
- Components: Single Sign-On
- Official update: https://status.okta.com/#incident/a9CWR0000002Hcg2AE

## Updates from Okta

### update, 2026-09-11 17:26 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 r

### update, 2026-09-03 14:09 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.

### update, 2026-09-03 13:03 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.

### update, 2026-09-03 12:30 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.

### update, 2026-09-03 12:00 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.

### update, 2026-09-03 11:34 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.

### update, 2026-09-03 11:02 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.

### update, 2026-09-03 10:42 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.