Identity & Access
Okta
Status detail
expected body marker missing: <channel>
30-day availability
73.63%
Downtime (30d)
20 min
Degraded (30d)
22742 min
Events (30d)
7
What this affects in your stack
If Okta is down, sign-in and SAML federation across your stack are blocked. Confirm scope on Okta status page, switch any production cutover to your IdP backup if you operate one, and post a customer-facing notice. Most outages resolve in <2h.
authidentity
Incident history (last 30 days)
| When | Type | Severity | Duration | Detail |
|---|---|---|---|---|
| 2026-06-01 20:40 | degraded | P1 | ongoing | HTTP 200 |
| 2026-06-01 20:30 | down | P0 | 9m | timeout |
| 2026-05-29 08:20 | degraded | P1 | 84h 10m | HTTP 200 |
| 2026-05-29 08:10 | down | P0 | 9m | timeout |
| 2026-05-21 02:55 | degraded | P1 | 197h 14m | HTTP 200 |
| 2026-05-21 02:35 | recovered | P4 | 0s | HTTP 200 |
| 2026-05-21 01:35 | degraded | P1 | 59m | HTTP 401 |
Quick links
Others in Identity & Access
Get alerted the moment Okta has an issue (and on your own services too)
ITIL Sidekick monitors every service you depend on with multi-sample consensus probing, full HTTP capture, and a cost ledger that tracks downtime impact in real time. 60-day trial, no credit card.
Start your free trial →