Okta Cell - EU1 has gone into Read Only Mode

Update timeline

1. investigating Oct 13, 2026, 07:25 AM UTC

   At 13/10/2026 00:50 PT, the team became aware of an issue with to our Core Platform service affecting customers in EMEA Cell 1. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. Affected cells: okta-emea.com:1

2. monitoring Oct 13, 2026, 08:40 AM 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.

3. resolved Oct 13, 2026, 09:08 AM 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.

4. resolved Oct 20, 2026, 07:19 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 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: Immediately upon receiving alerts, incident response processes were activated. On-call incident responders analyzed the database service failure and took actions to failover to a healthy primary and restore service functionality. Preventative Actions: In order to prevent and mitigate similar incidents in the future, Okta has currently implemented the following: - Improved alerting for faster impact analysis - Conducted a full scan of all database error log files to ensure this issue had not happened previously - Fixed a bug related to authentication failures during Read Only Mode related to Device Assurance checks Additionally, Okta is reviewing operating procedures to recover the service faster and is currently working with external infrastructure vendors to investigate the underlying cause of the database crash. Duration (# of minutes): 35