Okta outage, 22 June 2026
Elevated 500 or 502 Errors
- Started
- Resolved
- 22 Jun 2026, 22:02 UTC (after 40 min)
- Impact
- Major
- Affected
- Core Platform
Is this still happening?
No. Okta marked this incident resolved on 22 Jun 2026, 22:02 UTC, 40 min after it began.
Right now: Okta reports degraded performance on some systems. (as of 30 Oct, 12:04 UTC) Live Okta status
Last update from Okta
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 22nd, 2026, at 2:08 PM PDT, Okta internal monitoring alerted our team to errors in the EU environment. During this period, administrators and end users may have experienced intermittent 500 Internal Server Error and 429 Rate Limit responses when attempting to access Okta services. Root Cause Summary: The incident was triggered by an unexpected...
Similar Okta incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 7 h 34 min
-
, resolved after 1 h 20 min
-
, resolved after 42 min
-
, resolved after 36 min
-
, resolved