rewindex

ChangesOktaElevated 500 or 502 Errors

Okta: Major incident: Elevated 500 or 502 Errors

Major incidentoutage (model (Jev), 82%)Changed Detected status.okta.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Okta removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Elevated 500 or 502 Errors
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-06-22 21:22 UTC
AddedAffected components#5
Before: not present
After: Cell okta-emea.com:1, Core Platform / Core Service
AddedUpdateresolved#6
Before: not present
After: At 6/22/2026 2:22 PM PT, the team became aware of an issue with our Core Platform service affecting customers in EU Cell 1. During this time, users may experience intermittent failures and high latency when logging in or accessing the service. Our team is actively investigating this issue and is working to mitigate it. We will provide another update within the next 15 minutes, or sooner if additional information becomes available.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Monday, June 22

1 incident change

Cite this

Major incident: Elevated 500 or 502 Errors on Okta’s status page, changed 2026-06-22 21:22 UTC (change 1 of 1).

Title
Major incident: Elevated 500 or 502 Errors
Vendor
Okta
Date
URL
https://rewindex.com/change/i7103bee99af949

All Okta changesOkta profileMarkdownJSON