# Okta: Okta Cell - EU1 has gone into Read Only Mode

- Provider: [Okta](https://outages.cc/okta.md)
- Type: Incident
- State: Resolved
- Worst impact: Partial outage
- Started: 2026-10-13 07:25 UTC
- Resolved: 2026-10-13 23:59 UTC (lasted 16 h 35 min)
- Components: Core Platform
- Official update: https://status.okta.com/#incident/a9CWR0000002MXW2A2

## Updates from Okta

### update, 2026-10-20 19:19 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 October 10th at 12:50 AM PT, Okta’s monitoring systems alerted on-call teams to a database server issue on EMEA Cell EU1. During this time, administrators and end users may have encountered Read Only Mode (See KB: https://support.okta.com/help/s/article/What-is-Oktas-Readonly-Mode ) during this period, as well as errors related to write operations and certain authentication flows. Root Cause Summary: The root cause of the disruption was an unexpected crash of the primary data store supporting the impacted cell, which automatically resulted in Okta application servers transitioning to Read Only mode to ensure data integrity. Remediation Steps:

### update, 2026-10-13 09:08 UTC

The incident has been resolved. The services were in read only mode and actions were taken to restore service and return to normal operations. An RCA will be available within 5 business days.

### update, 2026-10-13 08:40 UTC

We have implemented a fix for the issue and are now seeing Okta Services restored. We will continue to monitor and provide an update in the next 30 mins.