Okta outage, 22 September 2025

Intermittent import issue with Google Groups Query API

Started
Resolved
22 Sept 2025, 18:21 UTC
Impact
Minor
Affected
Core Platform

Is this still happening?

No. Okta marked this incident resolved on 22 Sept 2025, 18:21 UTC.

Right now: Okta reports degraded performance on some systems. (as of 30 Oct, 12:14 UTC) Live Okta status

Last update from Okta

Incident start: September 15, 2025 Incident resolved: September 25, 2025 Detection: Okta was alerted to the issue after customers reported that groups managed by Google Workspace were being unexpectedly removed from Okta during the import process. Impact: Customers utilizing the Google Workspace integration may have experienced the following during this period: During scheduled or manual imports, groups (which still existed in Google Workspace) were unexpectedly removed from Okta. The unintended removal of groups may have resulted in a loss of application access for users who were members of the affected groups. Root Cause: The root cause was an issue within the Google Workspace Directory AP...

23 Oct 2025, 02:52 UTC

Read the full incident on the official Okta status page

Similar Okta incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 25 h 39 min

    Service Disruption in Google Workspace Imports

  2. , resolved after 1 h 30 min

    Latency Issue Affecting Google Imports

  3. , resolved after 7 h 34 min

    Group Push Delays on OK3

  4. , resolved after 1 h 20 min

    Group Push failures in EU1

  5. , resolved after 1 min

    Import slowness related to third-party provider

Other recent Okta incidents

  1. Office 365 Domain Federation Failures

  2. Degraded Performance: Delays in Outbound SMS Delivery

  3. Reporting Unavailable

  4. Okta Cell - EU1 has gone into Read Only Mode

  5. Service Disruption in Workflows

  6. Intermittent Access Issues with Office 365 Apps via Okta

  7. Issues with Custom Domains in Cell OK9

  8. Error 500 observed in OP1

All recorded Okta incidents