Is Okta down?
Vendor lists an old incident, not shown as liveWhat Okta reports
Okta still lists an incident opened on 2026-10-28 with no update since 2026-10-30; we do not show it as live.
As of the last successful poll, 2026-11-05 14:14 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked moments ago
Our checks of Okta pass from all 10 regions we check.
As of Nov 5, 2026, 2:34 PM UTC, RealUptime's checks of Okta passed in all 10 regions that returned a reading.
Okta publishes no status feed we can read, so the only reading here is our check reading on the left.
Okta response time, by region
Check your own site while you wait on Okta
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Okta. It cannot diagnose Okta's own systems.
What we measured, function by function
Okta answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Okta reports an incident on its status page, and again when it reports it resolved.
Get an email when Okta reports an incident
Email me when Okta reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 483msstatus code: 200checked: Nov 5, 2026, 2:34 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Okta normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 985msstatus code: 200checked: Nov 5, 2026, 2:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Okta normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 689msstatus code: 200checked: Nov 5, 2026, 2:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Okta normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 561msstatus code: 200checked: Nov 5, 2026, 2:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Okta normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 1445msstatus code: 200checked: Nov 5, 2026, 2:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Okta normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 320msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Okta normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 320msstatus code: 200checked: Nov 5, 2026, 2:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Okta normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 925msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Okta normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1636msstatus code: 200checked: Nov 5, 2026, 2:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Okta normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1349msstatus code: 200checked: Nov 5, 2026, 2:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Okta normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Okta, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Okta yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Okta since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Okta covering any window you pick, with our check readings and Okta's own claim at the time, side by side.
Full check history for Okta: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/okta)<a href="https://realuptime.io/outages/okta"><img src="https://realuptime.io/outages/okta/badge.svg?days=30" alt="Okta uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Okta down?", https://realuptime.io/outages/okta. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.
Host checked: login.okta.com