Vendor-reported status observed by INTERNETMON
Okta status
Okta · Okta Status
Okta exposes 21 public service cells and 0 active incident(s); it does not expose a complete product-component catalog.
Service cells and products
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
21
Retained
21
Affected retained
0
Projection scope: observed · 21 retained of 21 reported components.
okta.com:1
Operational
okta.com:2
Operational
okta.com:3
Operational
okta.com:4
Operational
okta.com:6
Operational
okta.com:7
Operational
okta.com:8
Operational
okta.com:9
Operational
okta.com:11
Operational
okta.com:12
Operational
okta.com:14
Operational
okta.com:16
Operational
okta.com:17
Operational
okta.com:18
Operational
okta.com:19
Operational
okta.com:20
Operational
okta.com:22
Operational
okta-emea.com:1
Operational
oktapreview.com:1
Operational
oktapreview.com:2
Operational
Showing 20 of 21 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 725.2 ms feed latency
Operational
HTTP 200 · 822.89 ms feed latency
Operational
HTTP 200 · 686.68 ms feed latency
Operational
HTTP 200 · 721.52 ms feed latency
Operational
HTTP 200 · 771.14 ms feed latency
Operational
HTTP 200 · 645.93 ms feed latency
Operational
HTTP 200 · 647.48 ms feed latency
Operational
HTTP 200 · 798.92 ms feed latency
Operational
HTTP 200 · 723.84 ms feed latency
Operational
HTTP 200 · 568.68 ms feed latency
Collection details
Provider adapter
Okta Status
Feed response
HTTP 200
Feed latency
640.6 ms
JSON source