Login Page Unavailable in OK6
Okta reports that the login page and sign-in requests can be unavailable or return errors for organizations in Cell OK6, which affects the Core Platform. Okta resolved this incident on November 9, 2026. The outage lasted about 97 minutes.
State
Resolved
Started
Lasted
1 h 37 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
25 min 26%
Monitoring
1 h 12 min 74%
Updates
Times in UTCAs posted by Okta
On November 9, 2026, at 9:20 AM PT, Okta became aware of an issue where the login page and sign-in requests for organizations in Cell OK6 may be unavailable or return errors. Users may be unable to sign in to Okta or to applications that rely on Okta. Our engineering team is actively investigating. We will provide an update within 30 minutes or as soon as more information is available.
On November 9, 2026, at 9:20 AM PT, Okta became aware of an issue where the login page and sign-in requests for organizations in Cell OK6 may be unavailable or return errors. Users may be unable to sign in to Okta or to applications that rely on Okta. Our engineering team is actively investigating. We will provide an update within 30 minutes or as soon as more information is available.
On November 9, 2026, at 9:20 AM PT, Okta became aware of an issue where the login page and sign-in requests for organizations in Cell OK6 may be unavailable or return errors. Users may be unable to sign in to Okta or to applications that rely on Okta. Our engineering team is actively investigating. We will provide an update within 30 minutes or as soon as more information is available.
Affected components
1Okta in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
67
Median duration
7 days
This incident
99% shorter than the median
Other Okta incidents
All incidentsOkta·Office 365 Domain Federation Failures
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.
Okta·Degraded Performance: Delays in Outbound SMS Delivery
Okta had degraded performance in its MFA service. Outbound SMS messages, including 2FA verification codes and SMS alerts, were delayed or failed. Okta reports that the issue is resolved. The outage lasted from October 28, 2026 to November 6, 2026.
Okta·Group Push Delays on OK3
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.
Okta·Reporting Unavailable
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.
Okta·Group Push failures in EU1
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.
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.
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.live/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.
https://outages.live/feed.xml?providers=okta/feed subscribe https://outages.live/feed.xml?providers=oktaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane