Okta Incident History

1. ResolvedSep 3 · 14:09 UTC

   After monitoring for an extended period, we confirmed that the issue has not reoccurred. A root cause analysis (RCA) will be posted here within five business days. We sincerely apologize for the impact this had on you and your users.

Reported by Okta on their status page.

1. ResolvedAug 1 · 03:28 UTC

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to our services to prevent future occurrences. Detection and Impact On July 24, 2026, at approximately 3:55 AM PDT, Okta observed service degradation for OK7, OK12, OK14, and OP3. The incident specifically impacted customers utilizing AD/LDAP delegated authentication and OAuth token-endpoint clients situated within the AWS us-west-2 region. Throughout the event, users encountered errors accessing resources, authentication failures, agent connection timeouts, latency, and OAuth token requests. Root Cause Summary The root cause originated from errors within a cloud service provider for the affected region. Remediation Steps The cloud service provider recovered connectivity, and Okta service stabilized by approximately 4:10 AM PDT, and our teams confirmed a complete return to baseline operations at 4:19 AM PDT. Preventative Actions Okta is actively reviewing and executing several initiatives to prevent future occurrences. These measures include: auditing and improving our incident response processes in the case of extended issues within a region, and refining our monitoring and alerting based on this incident. Total Duration Total Duration (Minutes): 15 minutes Start Time: 3:55 AM PDT End Time: 4:10 AM PDT Duration (# of minutes): 15

Reported by Okta on their status page.

1. ResolvedAug 21 · 16:04 UTC

   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 services attempted to send emails to recipient domains whose MX records pointed to Proofpoint’s infrastructure, the delivery attempts failed due to connection errors, resulting in deferred delivery. Okta’s email sending infrastructure operated normally throughout the event. Remediation Steps: Okta Engineering monitored service telemetry and confirmed that email delivery returned to normal pre-incident baselines once Proofpoint restored stability to its infrastructure. Preventive Actions: Okta is defining automated alerting thresholds for email-bound and deferral rates to decrease detection time and updating runbooks to allow faster diagnosis of downstream provider disruptions. Timing: Incident start: August 14, 2026, at 5:00 AM PDT Incident resolved: August 14, 2026, at 10:04 AM PDT. Duration (# of minutes): 304 minutes Based on details provided by https://www.proofpoint.com/us/support-services

Reported by Okta on their status page.