Okta experienced a minor incident on April 4, 2025 affecting OIG Access Requests, lasting 7d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Apr 04, 2025, 03:00 PM UTC
At 4/4/2025 8:00 AM PT, the team became aware of an issue with to our service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, US Cell 11, US Cell 12, US Cell 14. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next , or sooner if additional information becomes available. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11, okta.com:12, okta.com:14
- resolved Apr 04, 2025, 04:27 PM UTC
We're currently investigating an issue causing the degradation of OIG Access Requests. Our engineering team is actively working to identify and resolve the problem. We will provide another update in 30 minutes or less if more details become available.
- resolved Apr 04, 2025, 04:48 PM UTC
We're currently investigating an issue causing the degradation of OIG Access Requests. Our engineering team is actively working to identify and resolve the problem. We will provide another update in 30 minutes or less if more details become available.
- resolved Apr 04, 2025, 05:05 PM UTC
We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.
- resolved Apr 04, 2025, 05:06 PM UTC
We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.
- resolved Apr 04, 2025, 05:24 PM UTC
Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.
- resolved Apr 04, 2025, 05:50 PM UTC
Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.
- resolved Apr 04, 2025, 06:13 PM UTC
An issue impacting Okta Identity Governance (OIG) access requests for users in all US Production Cells has been resolved. Additional root cause information will be available within 5 Business days.
- resolved Apr 11, 2025, 09:37 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 Friday, April 4th at 7:59 am (PT), Okta’s monitoring systems alerted our Engineering team that some OIG users in US Commercial Cells were experiencing slow requests and request errors for governance requests via Okta Inbox. Retry attempts would eventually succeed. Root Cause Summary: Based on our investigation, an increase in a specific query requiring significant resources resulted in extra database load. This resulted in increased query latency, workload connection errors, and inbound API call failures. Remediation Steps: Upon receiving alerts, Okta began diagnosing the issue and launched a series of scaling activities. The team identified the root cause of the issue and took action to remediate the situation. At approximately 9:42 am (PT) Okta saw a decrease in query delays in the affected cell. At 9:43 am (PT) service latency returned to normal operation. Preventative Actions: To ensure this does not happen again, teams are remediating expensive database operations to prevent recurrence of this issue. Okta is looking into enhancing monitoring to identify expensive database operations faster. Additionally, runbooks are being updated to allow for faster remediation