Skip to main content
Okta logo

Is Okta Down?

No — Okta is up

Reachable from all 8 checked regions

Average response time: 144ms

Last checked · checks run every 6 hours

Official status page: https://status.okta.com

Okta uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
122ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means we have no measurement for that window.

30-day history

2-day clean streak
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: 100.00% uptime, 8 checks
Jul 28: 100.00% uptime, 24 checks
Jul 29: no data
Jun 30 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
241ms
DNS 0ms TCP 4ms TLS 8ms TTFB 207ms
arn
258ms
DNS 0ms TCP 1ms TLS 11ms TTFB 253ms
bom
289ms
DNS 1ms TCP 1ms TLS 7ms TTFB 280ms
nrt
65ms
DNS 0ms TCP 0ms TLS 9ms TTFB 59ms
ord
50ms
DNS 0ms TCP 2ms TLS 6ms TTFB 43ms
sin
42ms
DNS 0ms TCP 1ms TLS 4ms TTFB 36ms
sjc
33ms
DNS 0ms TCP 0ms TLS 5ms TTFB 28ms
syd
202ms
DNS 0ms TCP 0ms TLS 5ms TTFB 196ms
yyz
39ms
DNS 0ms TCP 1ms TLS 7ms TTFB 33ms

What Okta does

Okta is an identity provider handling single sign-on and multi-factor authentication for workforce and customer applications. When an organisation routes login for its whole application estate through Okta, an outage is not one application failing but every application refusing new sessions at the same moment.

What an outage looks like

When Okta is down, users cannot sign in to anything behind it: the login page fails to load or hangs after credentials are entered, and multi-factor prompts may never arrive. People holding a valid session usually keep working until it expires, so the impact spreads gradually through the day rather than hitting everyone at once.

What to do about it

Check status.okta.com and identify your cell, because availability is reported per cell rather than globally. Tell people not to sign out: existing sessions normally survive the incident and signing out cannot be undone. Break-glass administrator accounts that bypass the identity provider exist for this situation, and this is when they are used.

Is it down for everyone, or just you?

If this page says Okta is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Auth0 (Okta)
Auth0 (Okta)
Salesforce
Salesforce
Slack
Slack
AWS
AWS

Okta outage FAQ

Will I be logged out of everything if Okta goes down?
Usually not immediately. Applications generally accept an existing session until it expires, so people already signed in keep working. What fails is anything requiring a fresh authentication: new logins, new devices, and sessions that happen to time out during the incident. That is why signing out mid-outage is worth avoiding.
How do administrators get in during an Okta outage?
Through a break-glass account that authenticates locally rather than through the identity provider. Most organisations create these precisely so an identity outage does not lock everyone out of their own systems. If yours has not, an Okta incident is a bad time to discover it, and worth adding to the post-incident list.
Is Okta down or is my application misconfigured?
status.okta.com reports per cell, and your cell is identifiable from your Okta org URL. If your cell is healthy and only one application fails, the problem is more likely that application's integration than Okta itself. Check whether other applications behind the same identity provider are still accepting new logins.
Does an Okta outage affect Auth0?
Auth0 is operated as a separate platform with its own status page, so an Okta workforce incident does not automatically mean Auth0 is affected. Organisations using both should check each independently rather than assuming one status covers the other.

How we measure this

  • We request Okta's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Okta publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Okta goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required