Okta experienced a major incident on January 19, 2026 affecting okta-emea.com cell 1 and okta.com cell 1 and 1 more component, lasting 7d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jan 19, 2026, 06:10 PM UTC
At 1/20/2026 7:14 AM PT, Okta teams are aware of issues currently affecting Google Workspace imports. Admins may see "Unexpected Error" or "Missing Required Field" notifications within their dashboard. Our teams are investigating the root cause, and we will post another update in 30 minutes or sooner with more details.
- resolved Jan 20, 2026, 04:04 PM UTC
We've identified that the service interruption is due to an issue with a third-party provider. We are actively working with the provider to ensure a swift resolution and are closely monitoring progress. We will provide further updates as more information becomes available.
- resolved Jan 20, 2026, 04:35 PM UTC
We are continuing to monitor progress with our third-party provider. The provider is currently implementing mitigation steps, and we are seeing signs of recovery. Several customers have already confirmed that service has been restored on their end. We are working to ensure this resolution is consistent across all accounts. We will provide the next updates within 30 minutes, or sooner if additional information becomes available.
- resolved Jan 20, 2026, 05:10 PM UTC
Our third-party provider is continuing their recovery efforts. While we are no longer seeing active errors, we remain in a period of close monitoring as they work toward a final resolution. We recognize that some users may still experience residual effects; our Support teams are working with them to resolve these errors. Our next update will be in 60 minutes or sooner if additional information becomes available.
- resolved Jan 20, 2026, 05:21 PM UTC
Our third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.
- resolved Jan 26, 2026, 06:31 PM UTC
Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. Timing: Incident start: January 19, 2026, at 10:10 AM PST Incident resolved: January 20, 2026, at 11:49 AM PST Detection: Okta teams were notified via customer cases and an increase in Google Workspace import errors. Impact: Any customers performing Google Workspace imports during the incident window may have encountered an error stating “UserImportJob: Failed to download users. Json field=primaryEmail does not exist for object=[...]” Root Cause: Google Workspaces, a third-party provider, confirmed that a faulty code change introduced caused certain fields, such as primary email addresses, to be missing in API call results. As a result, Okta imports from Google Workspace could not complete, leading to import failures. Google provides additional details for this disruption: https://www.google.com/appsstatus/dashboard/incidents/9q5n4sfDnxYzHj8FxEua Remediation Steps: Okta teams soon identified that a provider-side disruption was the cause of the incident and opened a formal support case to track the resolution. The third-party provider resolved the incident by rolling back a faulty code change and restoring the missing metadata. Recovery occurred in stages, with some customers successfully remediated before others. Okta teams monitored the recovery in real-time and confirmed successful import signals across multiple impacted customers before standing down.