Okta's Single Sign-On component failed for Office 365 domain federation starting at 14:07 UTC, and the problem ran for 25h 55m before it was resolved. The fault sat on Okta's side of the federation link, not yours.
Started
14:07 UTC
Duration
Lasted 1d 1h
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: Single Sign-On, Single Sign-On
What happened?
Okta's status page lists one incident on this day, titled "Office 365 Domain Federation Failures", under the Single Sign-On component. It started at 14:07 UTC and ran for 25h 55m, which is long against Okta's own recent record: the last 90 days show 13 incidents with a median duration of 2 hours 35 minutes, so this one ran roughly ten times longer than typical. Okta published no updates during the window that this record captures, so there is no timeline of what was tried, what was found, or when federation actually started working again inside that 25h 55m span. No user reports were filed during the window on this page, which is unusual for an outage this long but is what the record shows. The component list names only Single Sign-On, and specifically the Office 365 federation path, so this was not a platform-wide Okta failure. If your product relies on Okta for signing users into Office 365 or similar federated services, this is the kind of fault that breaks that one login path while everything else about Okta, including its own dashboard and admin console, can look fine. Okta's 90 day history of 13 incidents at a pace of roughly one every week shows this is not a rare event for the service. Across all time, Okta logs an average of 2.5 incidents per month. No post-mortem has been published explaining why federation failed or what fixed it, so the cause is not on the record.
Learning
This incident shows the specific shape of a federation failure: the identity provider is up, the admin console works, but the handshake for one downstream service breaks, in this case Office 365 domain federation through Single Sign-On. Over the last 30 days, UptimeRobot's own checks against Okta recorded 9 incidents with a median duration of 2h 34m, close to the vendor's own 90 day median of 2 hours 35 minutes, which tells you this kind of disruption is a recurring pattern rather than a one-off. A check that only pings your own login page or your own servers will not catch this, because your servers are fine and the failure happens inside the federation exchange between Okta and Office 365. That is why external monitoring of the provider itself matters: it sees the handshake fail even when your own endpoints report green. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.