Okta Cell - EU1 has gone into Read Only Mode
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.
The latest update from Okta.
State
Resolved
Started
20 d ago
2026-10-13 07:25 UTC
Lasted
16 h 35 min
until 2026-10-13 23:59 UTC
Worst impact
Partial outage
Timeline
3 updatesUpdate
16 h 35 min 100%
Updates
Times in UTCAs posted by Okta
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:
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.
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.
Affected components
1Okta in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
61
Median duration
7 days
This incident
91% shorter than the median
Other Okta incidents
All incidentsOkta·Office 365 Domain Federation Failures
On October 29, 2026, at 6:45 AM PT, the Okta Engineering Team became aware of an issue with our domain federation management service. Administrators may be unable to add or update domain federations. Existing single sign-on (SSO) and end-user login sessions continue to function normally. Our engineering team is actively monitoring a high-priority vendor support ticket regarding an underlying database replication design change affecting federation management. We will provide another update as soon as additional information becomes available.
Okta·Degraded Performance: Delays in Outbound SMS Delivery
Okta reports delays or failures in outbound SMS delivery, including two-factor authentication codes, on the MFA component. The status is identified. Okta ties the issue to a service disruption at its downstream carrier, China Mobile. Users can use backup methods such as authenticator apps or email.
Okta·Group Push Delays on OK3
On October 21, 2026, at 11:49 AM PT, the Engineering Team became aware of an issue with Group Push affecting our customers in US Cell 3. Impacted customers may experience delays with group push imports. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Okta·Reporting Unavailable
On October 21, 2026, at 11:00 AM PT, Engineering became aware of an issue with our cloud vendor affecting reporting services on EMEA Cell 9. During this time, reporting will not be available. Our team is actively working with our cloud vendor to mitigate the issue. We will provide another update within the next 1 hour, or sooner if additional information becomes available.
Okta·Group Push failures in EU1
At 10/13/2026 6:00 AM PT, the Okta team became aware of an issue with Group Push affecting customer operations in EMEA Cell 1. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Follow Okta
Your coding agent knows when Okta is down, and tells you when a failure is theirs, not yours. You can also get Okta incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "okta" and tell me if Okta has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=okta/feed subscribe https://outages.cc/feed.xml?providers=oktaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane