Okta outage history

Okta Services / Workflows briefly experienced an outage as part of a quarterly breakglass test. The status update stated this was a test and to ignore it, and there were no user reports of impact.

The interruption began at 1:28 AM UTC and was resolved by 1:33 AM UTC, lasting about five minutes, with service returning to normal after the test.

Okta conducted a quarterly Breakglass drill that briefly affected the Third Party component, causing a short outage for users. The impact began at 12:58 AM UTC and was resolved by 1:09 AM UTC as the component recovered.

Okta's status page framed the event as a Breakglass test and explicitly noted it was not a real incident. The updates show the Third Party component moving from up to down and then back to up, with no ongoing impact after the drill; no user reports were observed during this period.

Users relying on Okta Workflows experienced failures as automated event triggers did not execute as expected. The disruption began around 1:17 PM UTC, and Okta indicated an ongoing investigation into a service disruption affecting Okta Workflows, with engineers analyzing logs and working on remediation. An update was promised within 30 minutes or as soon as additional information became available.

The outage lasted roughly nine hours and forty minutes and was resolved by 12:03 AM UTC when the Okta Workflows component returned to an operational state.

Users experienced intermittent access to Microsoft Office 365 apps (Outlook, Calendar, People) when launching them from the Okta Dashboard chiclets, receiving HTTP 401 Unauthorized errors caused by redirects. The issue began around 3:15 PM UTC and affected the Okta Services / Single Sign-On component as engineers investigated the root cause.

Okta confirmed the problem and, after a period of degraded sign-on, restored access by 11:03 PM UTC. The disruption appeared limited in scope, with user reports indicating sign-in problems until the service recovered.

Okta users trying to launch Microsoft Office 365 apps (Outlook, Calendar, and People) directly from the Okta Dashboard chiclets encountered intermittent access failures, returning HTTP 401 Unauthorized due to redirected login flows. The issue affected the Okta Services / Single Sign-On component, and Okta Engineering identified the root cause on Sep 15, 2026 3:15 PM UTC as they investigated.

Per the official updates, the outage window began at 2:33 PM UTC and the service was restored by 2:48 PM UTC. The disruption was brief and limited to the dashboard-based Office 365 app launches, with other Okta services remaining available.

Users attempting to launch Microsoft Office 365 apps (Outlook, Calendar, and People) directly from the Okta Dashboard chiclets experienced intermittent access issues, with HTTP 401 Unauthorized errors caused by redirect configurations. The disruption began at 2:23 PM UTC and was resolved about five minutes later at 2:28 PM UTC. The issue affected the Okta Services / Single Sign-On component and appeared to be limited to the dashboard launch flow rather than broader sign-on operations.

Okta Engineering identified the issue at Sep 15, 2026 3:15 PM UTC and published an update indicating ongoing investigation, with engineers working to restore normal access. The service returned to normal once the underlying redirects were addressed, and no wider outages were reported beyond the dashboard-triggered Office 365 integration.

Users attempting to launch Outlook, Calendar, and People directly from the Okta dashboard chiclets faced intermittent access issues, often receiving an HTTP 401 Unauthorized error due to redirect configurations. The problem centered on the Okta Services / Single Sign-On component and caused partial disruption for Office 365 integrations. Impact began around Sep 15, 2026 3:15 PM UTC and was resolved by Sep 16, 2026 2:18 PM UTC.

Users launching Microsoft Office 365 apps—Outlook, Calendar, and People—directly from the Okta Dashboard faced intermittent access issues, receiving HTTP 401 Unauthorized errors due to redirects. The impact began around Sep 15, 2026 3:15 PM UTC, with Okta Engineering actively investigating the root cause and confirming the problem centered on the Okta Services / Single Sign-On component.

On Sep 16, 2026 12:18 PM UTC, the status indicated a down condition for the SSO service, marking a partial outage. Access started returning to normal about an hour later, with service restored by Sep 16, 2026 1:13 PM UTC. Okta’s updates noted ongoing investigation into the root cause and described the disruption as impacting a subset of Office 365 app launch workflows managed through Okta.

Okta users briefly experienced intermittent access failures when launching Microsoft Office 365 apps (Outlook, Calendar, People) directly from the Okta Dashboard chiclets. Users could see HTTP 401 Unauthorized errors due to redirect configurations, preventing those apps from loading within Okta. The incident began at 12:08 PM UTC and was resolved by 12:13 PM UTC as Okta Engineering investigated and worked to restore access. The impact was limited to the Office 365 suite accessed via the Okta Dashboard.

Users launching Microsoft Office 365 apps directly from the Okta Dashboard chiclets experienced intermittent access with HTTP 401 Unauthorized errors caused by redirects. The disruption began at 11:34 AM UTC and lasted about nine minutes, with Outlook, Calendar, and People launches affected and then returning to normal by 11:43 AM UTC.

Okta Engineering identified an issue and began investigating. The impact was limited to the Office 365 app launch flow via Okta SSO, while other Okta services remained reachable.