Okta had two separate incidents on 21 October affecting its Core Platform and API Services components. Group push delays started at 19:15 UTC and ran for 2h 20m, and a reporting outage began at 20:08 UTC and lasted 3h 24m. Both were on Okta's side, not yours.
Started
19:15 UTC
Duration
Lasted 2h 20m
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: API Services, Core Platform
What happened?
Okta logged two incidents on 21 October 2026, both tied to the Core Platform and API Services components. The first, titled "Group Push Delays on OK3", started at 19:15 UTC and ran for 2h 20m. The second, "Reporting Unavailable", started at 20:08 UTC, overlapping the first, and ran for 3h 24m, making it the longer of the two. Okta published no updates on either incident beyond the initial listing, so there is no timeline of diagnosis, mitigation or fix to point to. No user reports were filed during the window on this record, which only tells you nobody logged a report here, not that nobody was affected. Okta's own status page groups both under the same two components, which suggests a shared dependency, but nothing in Okta's published record states a cause. With zero updates on either incident, you are left with the start times, the durations and the titles, and nothing else to go on. Over the past 90 days Okta has logged 12 incidents with a median duration of 2 hours 7 minutes, so a 3h 24m outage sits above that median. Across all time Okta has recorded 129 incidents, averaging 2.4 per month, so this kind of event is not rare for the platform.
Learning
If you only monitor your own login pages or API endpoints, an incident like "Group Push Delays" or a reporting outage can pass by without tripping your own checks, because your product may still respond fine while the underlying identity provider is degraded. These two incidents sat on Okta's side, affecting group push and reporting rather than every authentication flow, which is exactly the kind of partial failure that looks clean from outside unless something is watching the provider directly. UptimeRobot's own 30 day data shows 7 incidents recorded against Okta, all resolved, with a median duration of 2h 20m, which lines up with what happened here. That consistency matters: it means the gap isn't in your monitoring setup, it's in the layer below it, the one you don't control and Okta doesn't always explain. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.