Okta outage, 22 April 2026

Issue with 3rd party connectivity

Started
Resolved
22 Apr 2026, 16:14 UTC (after 6 min)
Impact
Minor

Is this still happening?

No. Okta marked this incident resolved on 22 Apr 2026, 16:14 UTC, 6 min after it began.

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

Last update from Okta

We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Customers using the third-party service Kolide began reporting that attempts to sign in to their orgs redirected to an unrelated tenant and received an HTTP 400 error with the message “Login Failed - 400: Bad Request Error Code: GENERAL_NONSUCCESS” Root Cause Summ...

6 May 2026, 07:14 UTC

Read the full incident on the official Okta status page

Other Okta incidents

  1. Office 365 Domain Federation Failures

  2. Degraded Performance: Delays in Outbound SMS Delivery

  3. Group Push Delays on OK3

  4. Reporting Unavailable

  5. Group Push failures in EU1

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

  7. Service Disruption in Workflows

  8. Intermittent Access Issues with Office 365 Apps via Okta

All recorded Okta incidents