outages.live
Live

Okta

Okta is reporting degraded

Checked 18 s ago Degraded

Degraded Performance: Delays in Outbound SMS Delivery

Okta reports delays or failures in outbound SMS delivery, including two-factor authentication codes, on the MFA component. The status is identified. Okta ties the issue to a service disruption at its downstream carrier, China Mobile. Users can use backup methods such as authenticator apps or email.

Degradedupdated 2 d ago

History

90 days agoToday

Incidents in 90 days

11

Days with an incident

61

Median duration

7 days

Longest incident

10 days

Components

9
API Services Operational
90 days ago8 days with an incidentToday
Advanced Server Access Operational
90 days agoNo incidentsToday
Core Platform Operational
90 days ago24 days with an incidentToday
Core Platform;MFA Operational
90 days ago8 days with an incidentToday
MFA Degraded
90 days ago5 days with an incidentToday
MFA;Single Sign-On Operational
90 days agoNo incidentsToday
OIG Access Requests Operational
90 days agoNo incidentsToday
Single Sign-On Operational
90 days ago23 days with an incidentToday
Workflows Operational
90 days ago9 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration26 h 21 min13:45 to 16:05Office 365 Domain Federation FailuresDegraded

On October 29, 2026, at 6:45 AM PT, the Okta Engineering Team became aware of an issue with our domain federation management service. Administrators may be unable to add or update domain federations. Existing single sign-on (SSO) and end-user login sessions continue to function normally. Our engineering team is actively monitoring a high-priority vendor support ticket regarding an underlying database replication design change affecting federation management. We will provide another update as soon as additional information becomes available.

Oct 21, 2026

Duration7 days18:49 to 22:34Group Push Delays on OK3Partial outage

On October 21, 2026, at 11:49 AM PT, the Engineering Team became aware of an issue with Group Push affecting our customers in US Cell 3. Impacted customers may experience delays with group push imports. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

Duration7 days18:00 to 22:34Reporting UnavailableDegraded

On October 21, 2026, at 11:00 AM PT, Engineering became aware of an issue with our cloud vendor affecting reporting services on EMEA Cell 9. During this time, reporting will not be available. Our team is actively working with our cloud vendor to mitigate the issue. We will provide another update within the next 1 hour, or sooner if additional information becomes available.

Oct 13, 2026

Duration7 days13:00 to 23:44Group Push failures in EU1Degraded

At 10/13/2026 6:00 AM PT, the Okta team became aware of an issue with Group Push affecting customer operations in EMEA Cell 1. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

Duration16 h 35 min07:25 to 23:59Okta Cell - EU1 has gone into Read Only ModePartial outage

At 13/10/2026 00:50 PT, the team became aware of an issue with to our Core Platform service affecting customers in EMEA Cell 1. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

Oct 1, 2026

Duration8 days13:17 to 03:44Service Disruption in WorkflowsPartial outage

On October 01, 2026, at 6:17 AM PT, we're investigating an issue with Okta Workflows where some automated event hook triggers aren't executing as expected. Our engineering team is actively analyzing system logs and working on root-cause remediation. We will provide an update within 30 minutes or as soon as additional information becomes available.

Sep 15, 2026

Duration10 days15:15 to 00:22Intermittent Access Issues with Office 365 Apps via OktaPartial outage

At 9/15/2026 8:15 AM PT, Okta Engineering has identified an issue causing intermittent access failures when users launch Microsoft Office 365 applications, specifically Outlook, Calendar, and People, directly from their Okta Dashboard chiclets. When clicking these application chiclets, the user will receive an HTTP 401 Unauthorized error due to configured redirects. We are actively investigating the root cause. Further updates will be provided as soon as more information becomes available.

Sep 11, 2026

Duration7 days12:10 to 21:37Issues with Custom Domains in Cell OK9Partial outage

At 11/09/2026 05:10 PT, Issues with Custom Domains in Cell OK9 - Customers with custom domains are currently experiencing issues in OK9. Engineering are currently investigating intermittent connectivity errors.

Sep 3, 2026

Duration8 days09:30 to 17:26Error 500 observed in OP1Degraded

At 9/3/2026 2:35 AM PT, the Engineering team became aware of an issue affecting customers in US Preview 1. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next hour, or sooner if additional information becomes available.

Aug 14, 2026

Duration7 days12:00 to 16:05Uptick in email deferralsDegraded

At 8/14/2026 7:35 AM PT, the Core Identity team became aware of an issue with email deliverability affecting customers in commercial cells. During this time, users may be experiencing intermittent issues receiving email from Okta. Our team is actively investigating this issue and is working to mitigate it.

Affected components

1
  • MFADegraded

Follow Okta

Your coding agent knows when Okta is down, and tells you when a failure is theirs, not yours. You can also get Okta incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "okta" and tell me if Okta has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=okta
Slack
/feed subscribe https://outages.cc/feed.xml?providers=okta

Go from tracking outages to fixing production issues with Polylane.

Try Polylane