Uptick in email deferrals
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.
The latest update from Okta.
State
Resolved
Started
79 d ago
2026-08-14 12:00 UTC
Lasted
7 days
until 2026-08-21 16:05 UTC
Worst impact
Degraded
Timeline
4 updatesUpdate
7 days 100%
Updates
Times in UTCAs posted by Okta
We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Okta detected an increase in customer support tickets regarding email delivery issues. Customers using custom email domains routed through Proofpoint experienced email delivery deferrals. During this period, affected end users were unable to receive system-generated emails, including One-Time Passwords (OTPs), account activation emails, password reset emails, factor enrollment emails, and other automated notifications. Root Cause Summary: Third-party provider Proofpoint experienced a service disruption, causing issues with email deliverability. When Okta ser
Our monitoring indicates that email deferrals to the impacted third-party email service have returned to the expected baseline. Additional information will be available within 5 Business days.
Okta Engineering has determined that certain third-party providers were failing to receive emails from Okta. Our monitoring shows delivery rates are recovering to normal conditions and will continue to monitor until full resolution. Our next update will be in 30 minutes or sooner if additional information becomes available.
Okta Engineering is investigating and has determined that the incident is currently impacting email delivery to a subset of customers. During this time, customers may experience email delivery deferrals. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.
Affected components
1Okta in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
61
Median duration
7 days
This incident
About 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 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.
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.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.
https://outages.cc/feed.xml?providers=okta/feed subscribe https://outages.cc/feed.xml?providers=oktaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane