Okta: Issue with 3rd party connectivity
Affected components: Cell okta-emea.com:1Cell okta.com:1Cell okta.com:2Cell okta.com:3Cell okta.com:4Cell okta.com:6Cell okta.com:7Cell oktapreview.com:1Cell oktapreview.com:2Cell okta.com:8Cell okta.com:9Cell okta.com:11Cell okta.com:12Cell oktapreview.com:3Cell okta.com:14Cell okta.com:16Cell okta.com:17Cell okta.com:18Cell okta.com:19Third Party
Timeline of updates
- resolved
On April 22, 2026, at 9:08 AM PT, we confirmed a third-party incident occurred with the Device Trust SAML authentication flow resulting in some users being redirected to an incorrect service provider between approximately 8:24 and 8:30am PT. This behavior originated from Kolide, a third-party middleware integration used for device trust signals and was isolated to organizations that use that specific security layer. While this resulted in users receiving 400 errors and being unable to access their intended applications, our investigation confirms that users were unable to access unauthorized applications or environments. Mitigation was in place by 8:30 AM PT, restoring service. A full root cause analysis will be forthcoming.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.okta.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Okta, started 2026-04-22 16:08 UTC, resolved after -968 min, 1 update(s).
- Title
- Issue with 3rd party connectivity
- Vendor
- Okta
- Date
- URL
- https://rewindex.com/company/okta/incidents/I-10482
Okta profileRecent Okta incidentsAll outages on April 22, 2026Okta in April 2026MarkdownJSON