Is Okta down right now?

No. Our checks are finding no problems with Okta right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Okta continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are can't log in, API errors, can't connect, website / app down, no response / timing out, 5xx error pages and slow or laggy. Those are the options the report button offers for Okta, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Okta specifically, Okta is the front door to everything else, so an Okta problem shows up as every other tool refusing to log in. Orgs are pinned to one regional cell, so your company can be locked out while another company's Okta is completely unaffected. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Okta, sign in to something that does not go through Okta. That working while everything behind Okta fails is them or your org's configuration. A colleague on a different network stuck at the same step rules out your device. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Okta's side. Specifically: stay signed in wherever you already are. Existing sessions usually survive an Okta incident and signing out during one can leave you unable to get back in. Do not re-enrol MFA, which needs the service you are waiting on. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Okta does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe okta.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Okta says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.okta.com, and it is linked further up this page. That is Okta's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Okta or okta.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Okta's own support, not us.