Okta favicon

Okta outage on 2026-10-28

okta.com
October 2026 28 Minor incident

Okta's MFA component started showing delays in outbound SMS delivery from 17:05 UTC on 28 October 2026. The fault sits with Okta, and as of the last check it is still open with no resolution posted.

Started

17:05 UTC

Duration

Lasted 8d 23h

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 logged one incident on this day, titled "Degraded Performance: Delays in Outbound SMS Delivery", starting at 17:05 UTC. It affects a single component, MFA. Okta has not posted any updates since the incident opened, so there is no timeline of escalation or recovery to report. The incident remains ongoing with no end time on record. No user reports were filed during this window, so there is no independent account of what this looked like for people trying to sign in with SMS-based MFA. If your product relies on Okta to send SMS codes for authentication, a delay here can mean users stuck waiting for a code that arrives late or not at all, even though your own login page is working fine. Okta's status page gives no cause, so there is nothing on record to explain why outbound SMS is delayed. Over the past 90 days, Okta has logged 12 incidents with a median duration of 2 hours 21 minutes, which gives a rough sense of how long this kind of thing tends to run, though this one has no confirmed end yet. Across all time, Okta averages 2.4 incidents a month, so a day like this is not unusual for the service. With zero updates posted since 17:05 UTC, anyone watching this page is working with the same single line Okta published and nothing more.

Learning

This is a case where the layer that failed sits well outside anything your own endpoint checks can see. Delays in outbound SMS delivery happen inside Okta's infrastructure, between Okta and the SMS carriers it uses, long before anything reaches your users' phones. Your own monitoring of your login flow would show green the whole time, because your application is correctly calling Okta and Okta is correctly accepting the request. The failure is in what happens after that handoff, where a text message either queues, delays or never arrives. UptimeRobot's own 30 day figures for Okta show 8 incidents with a median duration of 2 hours 20 minutes, a pattern consistent with what today's incident looks like so far. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.