Okta experienced a minor incident on June 11, 2025 affecting okta.com cell 4 and okta.com cell 6 and 1 more component, lasting 7d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jun 11, 2025, 06:13 PM UTC
At 6/11/2025 11:13 AM PT, the Okta Engineering team became aware of an issue with our service affecting customers in US Cell 4, US Cell 6, US Cell 7, US Cell 11, JP Cell 16. During this time, users may be experiencing elevated error rates within our system when attempting to connect to Okta service. Our team is actively investigating to mitigate the issue. We will provide another update within the next hour, or sooner if additional information becomes available.
- resolved Jun 11, 2025, 07:15 PM UTC
Services have been restored. We will continue to monitor the situation and we will provide another update within the next 60 minutes.
- resolved Jun 11, 2025, 07:30 PM UTC
The issue impacting multiple cells has been resolved. Additional root cause information will be available within 5 Business days.
- resolved Jun 18, 2025, 10:34 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 June 11th at 11:04 AM PT, Okta internal monitoring alerted on-call responders regarding a database issue across US Cells 4, 6, 7, 11, and 14. A subset of replica databases in the affected cells were deadlocking, resulting in slow query responses or timeouts. During this time, users and admins may have experienced request slowness and timeout errors. Auth rates and other user access was not impacted during this period. Root Cause Summary: Okta had progressively rolled out a configuration change earlier in the day as part of normal scheduled operations. This change exposed an error case which was then observed only in specific environments. Okta determined that MySQL contained a bug which, when a new specific monitoring query was executed, resulted in deadlocking the replica database servers and blocking additional queries from being executed. Remediation Steps: Upon investigation, at 11:11 AM PT Okta identified the root cause of the issue and began to execute database recovery efforts, thus restoring functionality and availability to normal operating levels. Impact Durations: US Cell 4 - 11:06 AM - 11:11 AM PT ~5 minutes US Cell 6 - 11:04 AM - 11:06 AM PT ~2 minutes US Cell 7 - 11:09 AM - 11:15 AM PT ~6 minutes US Cell 11 - 11:09 AM - 11:14 AM PT ~5 minutes US Cell 14 - 11:09 AM - 11:16 AM PT ~7 minutes Users may have continued to experience intermittent errors and delays in search results in cells while all database replicas were recovered. By 12:07 PM PT all databases had returned to normal operations. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: Review sequencing of database configuration updates deployed across environments These learnings work to prevent similar incidents from happening again.