Okta's MFA component logged a "Service Disruption on Email Delivery" lasting 42h 53m from 21:17 UTC on 12 November. The fault sat on Okta's side, not yours.
Started
21:17 UTC
Duration
Lasted 1d 18h
Source
IsDown
Next time
Okta is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: MFA, MFA
What happened?
Okta's own status page recorded a single incident on this day, titled "Service Disruption on Email Delivery", affecting the MFA component. It started at 21:17 UTC and ran for 42h 53m before resolution. Okta filed zero updates against this incident in the record, so there is no timeline of diagnosis, mitigation or fix to report. No user reports were filed during the window on this page, which only tells you nobody logged a report here, not that nobody was affected. Email-based MFA delivery failing for the better part of two days is long enough to lock people out of accounts that depend on email codes as a factor, if that is how your product configures Okta. Okta's history over the past 90 days shows 14 incidents with a median duration of 3 hours 7 minutes, so a single incident stretching to almost 43 hours sits well outside Okta's usual pattern. Over its all-time record Okta averages 2.5 incidents a month across 133 total incidents, so incidents themselves are not rare for this provider, but one running this long is. No post-mortem has been published explaining why email delivery for MFA took this long to restore. The cause is not on the record. Okta's status page is the only source here, and a single filing with no update history carries less weight than one with a documented timeline, so treat the 42h 53m duration as the vendor's own figure rather than an independently verified one.
Learning
UptimeRobot's own 30-day figures for Okta show 6 incidents, all 6 resolved, with a median duration of 14h 40m, which is itself far longer than Okta's self-reported 90-day median of 3 hours 7 minutes. That gap matters: Okta's status page reflects when Okta decided to open and close an incident, while external checks against Okta's endpoints measure when the service actually stopped answering correctly. An MFA email delivery fault like this one can run for hours without ever tripping a simple uptime check, because the authentication endpoint itself may keep responding even while a dependent delivery path, like email, is broken behind it. That is the general shape of this kind of failure, a healthy front door with a broken room behind it. If your own monitoring only watches your application's surface, it will show green the entire time your users are locked out by a factor they can't complete. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.