Okta Outage History

Started Feb 04, 2026, 10:41 AM UTC· resolved Feb 11, 2026, 06:45 PM UTC

1. resolved Feb 04, 2026, 10:41 AM UTC

   At 04/02/2026 02:41 PT, the team became aware of an issue with to our service affecting customers in EMEA Cell 9. 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 30 minutes, or sooner if additional information becomes available.

2. resolved Feb 04, 2026, 12:37 PM UTC

   Okta has implemented a fix for the LDAP issue affecting the OK9 environment. We are observing signs of service recovery and confirmed improvements from customers. We will continue to monitor the situation closely to ensure full resolution. We are monitoring the situation closely and will provide further updates within the next 30 minutes.

3. resolved Feb 04, 2026, 12:50 PM UTC

   This incident has been resolved. Internal monitoring and customer reports confirm that the LDAPi system in OK9 has fully recovered and is operating normally. We will continue to closely monitor the service to ensure stability. A full Root Cause Analysis (RCA) will be made available within 5 days. We apologize for any disruption this may have caused.

4. resolved Feb 11, 2026, 06:45 PM UTC

   On February 4th, 2026, at 3:33 AM PT, Okta received customer reports of authentication failures within the OK9 (EMEA) cell. Customers attempting to access LDAP interface services encountered certificate validation errors related to hostname mismatches, preventing successful authentication. Root Cause Summary: The incident was triggered by a misconfiguration introduced during a scheduled update of our LDAP interface to a new configuration source on February 4th 2:24 AM PT. This update inadvertently applied an incorrect SSL certificate profile to the LDAP interface within the OK9 environment. This misconfiguration caused certificate validity errors, resulting in connection issues when attempting to use LDAP services. Remediation Steps: Once the source of the issue was identified, Okta engineering team rolled back changes at 4:07 AM PT. These actions successfully addressed the issue and restored normal operations by 4:26 AM PT. Preventative Actions: To prevent future incidents, Okta has updated synthetic tests and enhanced monitoring. Teams also plan to add new tooling to improve changes to the LDAP service certificates. In addition, we are reviewing our internal processes and procedures, refining our automated rollback processes to further reduce the customer impact time for similar issues in the future. Duration (# of minutes): Total Duration (Minutes): 122 minutes Actual Time: 02:24 AM PT - 04:26 AM PT

Read the full incident report →

Started Jan 28, 2026, 03:30 PM UTC· resolved Apr 15, 2026, 11:37 PM UTC

1. resolved Jan 28, 2026, 03:30 PM UTC

   Okta is aware of the intermittent latency and connection issues affecting OK9 at approximately 07:30 AM PT due to a service disruption in one of the third-party providers. The provider reports early signs of recovery and recommends that users continue retrying failed requests, as success rates are expected to improve steadily. We are monitoring the situation closely and will provide further updates as we move toward full mitigation.

2. resolved Jan 28, 2026, 07:24 PM UTC

   We are seeing significant and steady system stability as our third-party provider recovery continues in the EU-West-1 region. We will continue monitoring the service to ensure a full recovery. We will provide another update in 60 minutes or as soon as more information becomes available.

3. resolved Jan 28, 2026, 07:36 PM UTC

   The third-party provider has confirmed that the issue has been resolved. A root cause analysis (RCA) will be posted here within five business days.

4. resolved Feb 05, 2026, 01:26 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: On January 29th, 2026, at 8:28 AM PT, Okta internal monitoring alerted our team of intermittent connectivity issues accessing Okta Cell 9 (EMEA). During this period, customers may have experienced intermittent errors establishing network connections and latency when trying to access Okta services. Clients configured to retry failed connections likely saw successful connectivity on secondary attempts. Root Cause Summary: The incident stemmed from a failure of a component that manages configuration changes to the networking infrastructure with our Cloud Service Provider (CSP) in the region hosting Okta Cell 9. Remediation Steps: Immediately upon receiving the alerts, Okta Engineering began investigating several isolated spikes but determined that cell health was stable. At 9:35 AM PT, Okta Engineering received more alerts and immediately initiated incident response procedures. At 9:51 AM PT, Okta Engineering began working with the CSP to diagnose the issue. At 10:13 AM PT, the latency began to stabilize. At 11:22 AM PT, the issue was resolved. Preventative Actions: To prevent similar incidents from recurring, Okta Engineering is improving our monitoring, working with our CSP to enhance their monitoring, and reviewing incident response processes associated with this event. Duration (# of minutes): 186

Read the full incident report →

Started Jan 22, 2026, 06:55 PM UTC· resolved Jan 30, 2026, 10:35 PM UTC

1. resolved Jan 22, 2026, 06:55 PM UTC

   The third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.

2. resolved Jan 22, 2026, 09:46 PM UTC

   We are continuing to monitor the third-party email service provider's progress toward a resolution. At this time, we have not received an estimated time for recovery (ETR). If you are attempting to sign in and have configured alternative MFA factors (such as Okta Verify, SMS, or Security Keys/Biometrics), we recommend using those options to avoid delays associated with email delivery. Our engineering teams remain on standby to verify service restoration the moment it begins. We will continue to provide updates as soon as the impacted provider shares new information.

3. resolved Jan 22, 2026, 11:24 PM UTC

   We're continuing to track the ongoing service disruption with the third-party email provider. We appreciate your patience while we await the provider's resolution of the root cause. We'll post our next update in 90 minutes or as soon as we have a significant change in status.

4. resolved Jan 23, 2026, 12:46 AM UTC

   The third-party email provider has identified the root cause as a service infrastructure issue within the North America region. They are currently implementing load-balancing configurations to stabilize the environment. While recovery is underway, users may continue to experience intermittent delays or failures in receiving emails. We are monitoring the provider's progress and will provide another update as they move toward full resolution.

5. resolved Jan 23, 2026, 03:55 AM UTC

   The third-party provider continues to see improvements across their impacted North American infrastructure. While our internal systems remain healthy, our team is on standby to validate the restoration of all external dependencies. We will provide a final update once the provider confirms that their services have fully returned to normal operations.

6. resolved Jan 23, 2026, 06:46 AM UTC

   The third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.

7. resolved Jan 30, 2026, 10:34 PM UTC

   Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service Timing: Incident start: January 22, 2026, at 10:55 AM PST Incident resolved: January 22, 202,6 at 7:50 PM PST Detection: The issue was initially identified through customer reports that they were not receiving expected email notifications. Okta Engineering confirmed the service disruption after internal monitoring indicated a high volume of deferred email delivery attempts to specific third-party domains. Impact: Customers across all Okta cells with email addresses hosted by Microsoft Exchange Online may have experienced intermittent delays or failures in receiving automated email notifications, such as Multi-Factor Authentication (MFA) codes and enrollment links. Okta services remained healthy and attempted to resend deferred messages. Root Cause: Microsoft reports that it experienced a service issue within its North American data centers during a planned maintenance activity. As a result, emails sent from Okta to the affected provider resulted in “soft bounce” errors, indicating that the provider’s servers were temporarily unable to accept the messages. Remediation Steps: To mitigate the impact on users attempting to sign in, Okta recommended using alternative MFA factors, such as Okta Verify, security keys, or SMS, to bypass delays associated with email delivery. Okta Engineering continuously monitored the third-party provider’s recovery efforts and validated that mail delivery returned to baseline levels once the provider stabilized their environment.

Read the full incident report →

Started Jan 19, 2026, 06:10 PM UTC· resolved Jan 26, 2026, 06:34 PM UTC

1. resolved Jan 19, 2026, 06:10 PM UTC

   At 1/20/2026 7:14 AM PT, Okta teams are aware of issues currently affecting Google Workspace imports. Admins may see "Unexpected Error" or "Missing Required Field" notifications within their dashboard. Our teams are investigating the root cause, and we will post another update in 30 minutes or sooner with more details.

2. resolved Jan 20, 2026, 04:04 PM UTC

   We've identified that the service interruption is due to an issue with a third-party provider. We are actively working with the provider to ensure a swift resolution and are closely monitoring progress. We will provide further updates as more information becomes available.

3. resolved Jan 20, 2026, 04:35 PM UTC

   We are continuing to monitor progress with our third-party provider. The provider is currently implementing mitigation steps, and we are seeing signs of recovery. Several customers have already confirmed that service has been restored on their end. We are working to ensure this resolution is consistent across all accounts. We will provide the next updates within 30 minutes, or sooner if additional information becomes available.

4. resolved Jan 20, 2026, 05:10 PM UTC

   Our third-party provider is continuing their recovery efforts. While we are no longer seeing active errors, we remain in a period of close monitoring as they work toward a final resolution. We recognize that some users may still experience residual effects; our Support teams are working with them to resolve these errors. Our next update will be in 60 minutes or sooner if additional information becomes available.

5. resolved Jan 20, 2026, 05:21 PM UTC

   Our third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.

6. resolved Jan 26, 2026, 06:31 PM UTC

   Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. Timing: Incident start: January 19, 2026, at 10:10 AM PST Incident resolved: January 20, 2026, at 11:49 AM PST Detection: Okta teams were notified via customer cases and an increase in Google Workspace import errors. Impact: Any customers performing Google Workspace imports during the incident window may have encountered an error stating “UserImportJob: Failed to download users. Json field=primaryEmail does not exist for object=[...]” Root Cause: Google Workspaces, a third-party provider, confirmed that a faulty code change introduced caused certain fields, such as primary email addresses, to be missing in API call results. As a result, Okta imports from Google Workspace could not complete, leading to import failures. Google provides additional details for this disruption: https://www.google.com/appsstatus/dashboard/incidents/9q5n4sfDnxYzHj8FxEua Remediation Steps: Okta teams soon identified that a provider-side disruption was the cause of the incident and opened a formal support case to track the resolution. The third-party provider resolved the incident by rolling back a faulty code change and restoring the missing metadata. Recovery occurred in stages, with some customers successfully remediated before others. Okta teams monitored the recovery in real-time and confirmed successful import signals across multiple impacted customers before standing down.

Read the full incident report →

Started Dec 26, 2025, 08:30 AM UTC· resolved Jan 03, 2026, 01:52 AM UTC

1. resolved Dec 26, 2025, 08:30 AM UTC

   Around 3:30 AM PT on December 26, 2025, the Engineering team became aware of an issue affecting customers on Ok6 cells. We temporarily put the cell in read-only mode. During this time, customers on OK6 were still able to log in and access apps, but could not create or modify any data, users, or settings. The issue has been resolved at 5:43 AM PST. Additional root cause information will be available within 5 Business days.

2. resolved Jan 03, 2026, 01:52 AM 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 are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this kind. Detection and Impact: On December 26, 2025, at 3:27 AM PST, Okta engineering was alerted to increased errors in US Cell 6. During this time, US Cell 6 experienced errors, connection timeouts, and slow responses while attempting to access resources. Admins would have seen a banner on the admin portal stating that the cell was in read-only mode. Root Cause Summary: Okta has determined that the issue was caused by an outage with our cloud service provider. All instances fully recovered by 5:43 AM PT. Remediation Steps: Upon detection, Okta’s engineering teams immediately began diagnosing the issue and worked with our cloud service provider to resolve the issue. In addition, the Incident response teams continued to review and analyze the incident, applying additional measures to improve service availability for end-user authentications. Preventative Actions: Okta is taking steps to prevent a recurrence of this issue. We are making improvements to our monitoring and response procedures to more quickly diagnose and recover from this kind of failure in the future. Total Duration: 2 hours and 16 minutes Start Time: December 26, 2025, 03:27 AM PT End Time: December 26, 2025, 05:43 AM PT

Read the full incident report →

Started Dec 14, 2025, 11:00 AM UTC· resolved Dec 23, 2025, 02:50 PM UTC

1. resolved Dec 14, 2025, 11:00 AM UTC

   At 12/14/2025 3:00 AM PT, the Okta Engineering team became aware of an intermittent issue with email being sent through Custom Email Domains. This is affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 7, EMEA Cell 9, US Cell 12, US Cell 14, US Preview 3. Our team is actively investigating this issue and working with our third-party vendor to address the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

2. resolved Dec 14, 2025, 04:40 PM UTC

   The Okta Engineering team is continuing to work with our third-party vendor and addressing this issue with urgency related to the custom domain email delivery issues.

3. resolved Dec 14, 2025, 04:42 PM UTC

   The next update will be posted in the next 60 minutes.

4. resolved Dec 14, 2025, 05:50 PM UTC

   Our Engineering team is continuing to work with the third-party provider on mitigation actions to help resolve this outstanding issue. We are treating the issue with the utmost urgency to restore our services as soon as possible. The next update will be provided within the next 60 minutes or sooner, if additional information becomes available.

5. resolved Dec 14, 2025, 06:48 PM UTC

   We have identified a potential root cause of this issue, and are currently investigating next steps towards resolution. We will provide the next update in 60 minutes, unless new information becomes available.

6. resolved Dec 14, 2025, 07:39 PM UTC

   This issue has been successfully resolved as of 11:07AM PDT. All services have been restored. If you continue to see issues, please update your support case for assistance. Additional root cause information will be available within 5 Business days.

7. resolved Dec 23, 2025, 02:49 PM 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 are the facts regarding this incident. We are committed to implementing improvements to the service to prevent similar future occurrences. Detection and Impact: On December 14, 2025, at 3:01 a.m. PST, Okta detected an issue that prevented email delivery for customers using custom email domains. This affected end-users' ability to receive emails for Multi-Factor Authentication (MFA), password resets, registration activation, account lockout notifications, and other notification emails, such as rate-limit notifications for administrators. Root Cause Summary: Okta has determined that the issue was caused by an unintended configuration change on our Mail Transfer Agents (MTAs). This change incorrectly routed emails from custom domains without proper DMARC sender authentication. As a result, email service providers rejected the emails, causing the delivery failures. Remediation Steps: Upon detection, Okta’s engineering teams immediately began diagnosing the delivery failures. After identifying the incorrect routing, we updated the configuration to ensure emails were sent through the appropriate authenticated channels. Normal email functionality was fully restored after the updated configuration was applied. Preventative Actions: Okta is taking several steps to prevent a recurrence of this issue. We are enhancing our monitoring and alerting for email services and improving our configuration management tools to add further safeguards. Duration (# of minutes):1140

Read the full incident report →

Started Dec 10, 2025, 07:42 AM UTC· resolved Dec 18, 2025, 02:29 AM UTC

1. resolved Dec 10, 2025, 07:42 AM UTC

   Okta Engineering became aware of an increase in connections on custom domain routers affecting customers in Cell OK9. Our team is actively investigating this issue to determine the root cause and mitigate the impact. During this time, users accessing their Okta tenant via custom domains may experience intermittent connectivity issues, including timeouts, latency, or 503/504 error messages. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

2. resolved Dec 10, 2025, 09:23 AM UTC

   Okta Engineering has implemented a mitigation for the issue affecting custom domain routers on Cell OK9. We are currently observing improvements in connection stability and a reduction in error rates. We will continue to monitor the service closely to ensure full resolution. Users accessing their Okta tenant via custom domains should see a return to normal performance. However, some customers may experience residual intermittent latency or errors while the system fully stabilises. We will provide another update within the next 30 minutes or upon full resolution.

3. resolved Dec 10, 2025, 10:01 AM UTC

   Okta Engineering has resolved the issue affecting custom domain connectivity on Cell OK9. Following the mitigation of the connection issues, we have confirmed that service performance has fully stabilised and all systems are operational. Additional root cause information will be available within 5 Business days.

4. resolved Dec 18, 2025, 02:29 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: On December 9th at 11:42 PM PT, Okta's monitoring systems alerted on-call teams to potential intermittent connectivity issues in custom domain EMEA Cell OK9. A subset of users attempting to access EMEA Cell OK9 custom domain organizations from specific geo locations, particularly France, experienced intermittent connectivity issues, including timeouts, latency, and/or 500 response errors when accessing Okta services. Users and clients accessing the custom domain resources that were not routed through these Point of Presence (PoP) network locations would not be impacted. Service was fully restored by 1:24 AM PT on December 10th. Root Cause Summary: The temporary disruption of network resources at certain Points of Presence stemmed from overly restrictive traffic limits that were distributed globally. These changes were implemented as a critical component of our broader, ongoing strategy to upgrade network infrastructure. The overly protective logic incorrectly caused the system to profile traffic across all global locations simultaneously. This resulted in the observed connectivity issues in European regions, particularly in France, during their local morning traffic ramp-up. Remediation Steps: Upon discovery, Okta swiftly determined the cause and worked with our Cloud Service Provider on implementing mitigation measures and rolling back changes. These steps successfully stabilized connectivity, restoring normal operations by 1:24 AM PT. Preventative Actions: We continue to closely collaborate with our Cloud service provider to comprehensively review and enhance our edge configurations, with the focused goal of establishing a more resilient and reliable infrastructure service capacity. Our unwavering priority remains the continuous optimization of our systems to safeguard against future events. Duration (# of minutes): Total Duration (Minutes): 102 minutes Actual Time: 11:42 PM PT - 01:24 AM PT (12/10)

Read the full incident report →

Started Dec 04, 2025, 08:31 AM UTC· resolved Dec 12, 2025, 04:32 PM UTC

1. resolved Dec 04, 2025, 08:31 AM UTC

   At 12/4/2025 12:31 AM PT, the team became aware of an issue with our LDAPi service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, and 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.

2. resolved Dec 04, 2025, 09:08 AM UTC

   The Okta Engineering has implemented mitigations and we are monitoring for recovery and will post another update in 30 minutes.

3. resolved Dec 04, 2025, 09:25 AM UTC

   Current mitigations are working and we are seeing recovery across all impacted cells. Customers should be able to successfully connect to Ldap at this point. If you experience further issues, please reach out via support and full RCA will be available within 5 business days.

4. resolved Dec 12, 2025, 04:32 PM 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 are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On December 3rd, at 11:51 pm PST, Okta received an alert concerning an error affecting LDAP services across multiple production cells. Root Cause Summary: Okta has determined that this issue was related to recent changes initiated by our Cloud Service Provider as a part of resiliency improvements. Remediation Steps: Okta began diagnosing the issue immediately upon receiving reports and determined that the issue was related to the vendor’s recent changes, which were implemented to improve our resiliency as a result of previous incidents. While engaging with the Cloud Service Provider’s support team, we were able to fully restore normal functionality. Preventative Actions: Okta is reviewing and enhancing its monitoring and alerting processes to minimize the impact on customers for similar issues in the future. Duration (# of minutes): 87 minutes

Read the full incident report →

Started Dec 03, 2025, 01:15 PM UTC· resolved Jan 26, 2026, 08:26 PM UTC

1. resolved Dec 03, 2025, 01:15 PM UTC

   At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. 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 30 minutes, or sooner if additional information becomes available.

2. resolved Dec 03, 2025, 01:57 PM UTC

   At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. During this time, users may be experiencing intermittent issues within our system. Our team is continuing to actively investigate and mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

3. resolved Dec 03, 2025, 02:32 PM UTC

   At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. 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 30 minutes, or sooner if additional information becomes available.

4. resolved Dec 03, 2025, 03:02 PM UTC

   At 12/3/2025, 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. Users may continue to experience intermittent issues within our system. We are actively working on mitigation efforts and will provide an update in the next 60 minutes.

5. resolved Dec 03, 2025, 03:50 PM UTC

   Our service is seeing recovery following successful mitigation efforts with our provider. We continue to closely monitor system stability. Our next update will be in 30 minutes, or sooner if new information is available.

6. resolved Dec 03, 2025, 04:24 PM UTC

   We are continuing to monitor the situation. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

7. resolved Dec 03, 2025, 04:58 PM UTC

   An issue impacting the core authentication service for customers in Okta Cell US7 has been resolved. Additional root cause information will be available within five business days.

8. resolved Dec 10, 2025, 07:51 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: On December 2nd, 2025, at 10:22 PM PT, Okta was alerted to a substantial increase in request traffic by Okta’s external monitoring as well as our Cloud Service Provider in US Cell 7 for custom domains. (Wave 1). Later, on December 3rd, 2025, at 4:48 AM PT, Okta was again alerted to a substantial increase in network traffic in US Cell 7 for custom domain supporting resources, and the traffic pattern was not detected by the Cloud Service Provider. (Wave 2). During these times, customers who utilize customized domains experienced outage errors or intermittent slowness when attempting to access the service. Root Cause Summary: Okta determined the root cause was a substantial increase in request network traffic volume, which resulted in errors and slow response times accessing the cell. Remediation Steps: Wave 1: At 10:36 PM PT, Okta Engineering initiated response procedures based on the observed service impact. Per operating procedures, the Cloud Service Provider’s system initiated mitigating actions. At 11:04 PM PT, Okta Engineering observed that the network traffic load had been mitigated and returned to normal processing levels. Wave 2: At 5:20 AM PT, traffic for Enhanced DR customers with custom domains was redirected to the rescue cell. At 5:27 AM PT, Okta Engineering scaled out infrastructure resources in an attempt to minimize the impact during this time. At 5:56 AM PT, Okta further scaled out the infrastructure, but saw only minimal recovery. The Cloud Service Provider applied similar restrictions, which partially mitigated the traffic flood. At 6:20 AM, Okta took additional measures to isolate the custom domain resource stack and began moving custom domains to this new stack in coordination with our support teams. Upon further examination of the issue by Okta and after gaining an understanding of the new network flows, at 7:04 AM PT, the Cloud Service Provider updated the mitigations and immediately observed a return to normal processing levels. Preventative Actions: To prevent similar incidents from recurring, Okta Engineering is collaborating with our Cloud Service Provider to understand better and analyze their overall alert triggering logic and review the processes associated with this event. We have also implemented additional protections in conjunction with our Cloud Service Provider. Duration (# of minutes): Wave 1: Total Duration (Minutes): 42 minutes Actual Time: 10:22 PM - 11:04 PM PT Wave 2: Total Duration (Minutes): 136 minutes Actual Time: 4:48 AM - 7:04 AM PT

Read the full incident report →

Started Nov 17, 2025, 06:34 PM UTC· resolved Nov 25, 2025, 12:21 AM UTC

1. resolved Nov 17, 2025, 06:34 PM UTC

   We detected a service interruption that impacted all users for approximately 10 minutes at 10:34 AM PT. Users may have encountered intermittent delays, connection errors, or 503/504 error messages. The issue is no longer active. We are monitoring for residual effects and will provide an update in the next 30 minutes.

2. resolved Nov 17, 2025, 07:44 PM 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.

3. resolved Nov 25, 2025, 12:21 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: On November 17th at 10:35 AM (PT), Okta received alerts regarding resource access errors in US Cell 14. During this time, customers in US Cell 14 experienced errors, connection timeouts, and slow responses while attempting to access resources. This incident was isolated to their cell, and normal processing levels were restored at 10:45 AM (PT). Root Cause Summary: Okta determined the root cause was a substantial increase in request traffic volume, which resulted in errors accessing the cell. Remediation Steps: The system automatically initiated service protection within 1 minute of a traffic increase, followed by additional resource scaling actions. These automated actions addressed the issue, and the team confirmed that response times and rates had fully returned to normal by 10:45 AM(PT). Incident response teams continued to review and analyze the incident, applying additional service protection configurations to improve service resiliency immediately after the service was confirmed to be stable. Preventative Actions: In order to prevent similar incidents from recurring, Okta is working in collaboration with our service provider to explore opportunities for enhanced scalability and faster mitigation action thresholds where necessary. We are fully committed to improving our infrastructure to ensure the reliability of our services. Our priority remains the continuous optimization of our systems to safeguard against future events. Duration (# of minutes): 11 minutes Actual Time: 10:34 AM - 10:45 AM PST

Read the full incident report →

Started Nov 12, 2025, 07:40 PM UTC· resolved Jan 26, 2026, 08:25 PM UTC

1. resolved Nov 12, 2025, 07:40 PM UTC

   Our Engineering team became aware of delivery delays in SMS MFA affecting US customers across all cells. Okta continues to monitor the current situation with our third-party provider. We recommend using alternative verification methods at this time.

2. resolved Nov 12, 2025, 08:56 PM UTC

   Our third-party vendor is making continuous progress on resolving the SMS delivery issues. Okta has also deployed additional safeguards on our platform to mitigate the impact. We will maintain active monitoring until we confirm the issue is fully resolved.

3. resolved Nov 14, 2025, 01:24 AM 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.

4. resolved Nov 19, 2025, 10:17 PM UTC

   Timing: Incident start: November 12, 2025, at 6:50 AM PST Incident resolved: November 12, 2025, at 12:50 PM PST Detection: Okta monitoring detected a significant decline in SMS deliverability rates, coinciding with customer reports of users not receiving SMS-based one-time passcodes (OTPs). Our third-party vendor subsequently updated their status page, confirming delivery delays to multiple networks in the United States. Impact: A subset of Okta customers experienced failures when attempting to receive SMS OTPs on their first attempt during the incident window. Although the initial delivery would fail, Okta offers the option to retry sending the SMS OTP, which is handled by a secondary provider. To leverage this secondary provider, end users were required to manually click the “Resend” button after the initial send failure. Users who performed this action were able to successfully receive their OTPs and authenticate. Root Cause: Okta’s primary third-party telephony provider experienced a service outage within their United States SMS delivery infrastructure. This outage caused deliverability rates for SMS messages routed through this provider to drop below acceptable thresholds. Remediation Steps: Okta Engineering updated the telephony configuration to swap our primary provider with our secondary provider for messages sent to US numbers. This change, completed at 12:50 PM PST, routed all new SMS traffic away from the impacted provider, restoring deliverability for first-attempt SMS requests. This configuration remained in place until the third-party vendor confirmed the resolution of their infrastructure issues and testing confirmed that deliverability rates were restored.

Read the full incident report →

Started Oct 29, 2025, 06:40 PM UTC· resolved Nov 05, 2025, 06:55 PM UTC

1. resolved Oct 29, 2025, 06:40 PM UTC

   We are aware that some services may be degraded as our third-party vendors are currently experiencing issues. We are actively investigating the scope of the impact and coordinating closely with our providers on a resolution. We will provide an update as soon as more information is available.

2. resolved Oct 29, 2025, 07:16 PM UTC

   We have confirmed that a third-party provider issue is causing intermittent timeouts when authenticating to the Microsoft O365 portal via Okta Verify. This is impacting a subset of customers. Our provider is actively addressing the issue, and we are closely monitoring their progress on the fix. We will provide the next update in 30 minutes.

3. resolved Oct 29, 2025, 07:54 PM UTC

   We appreciate your continued patience as we work through this service degradation. Our provider has successfully deployed a fix, and our team is now actively monitoring the environment and performance to confirm full stability. We understand the impact this has on your work, and we are committed to keeping you informed. We will provide our next scheduled status update in 120 minutes, or sooner if we achieve a significant update or confirm a complete fix.

4. resolved Oct 29, 2025, 11:22 PM UTC

   Remediation work by our third-party provider is ongoing, and Okta is observing consistent recovery across affected cells. Our next scheduled update is within 90 minutes or earlier if additional information becomes available.

5. resolved Oct 30, 2025, 01:47 AM UTC

   After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved by our third-party provider. Additional root cause information will be available within five business days.

6. resolved Nov 05, 2025, 06:54 PM UTC

   Timing: Incident start: October 29, 2025, at 7:15 AM PDT Incident resolved: October 29, 2025, at 4:05 PM PDT Detection: Okta monitoring detected errors when redirecting to Microsoft. Concurrently, customers began reporting intermittent timeouts when authenticating to Microsoft services and when using Okta Verify. Impact: A subset of customers experienced intermittent timeouts and SSO login failures when authenticating to Microsoft services (such as Microsoft 365). Further, customers may have seen timeouts in Azure webhooks and other redirects to Microsoft services. Root Cause: Microsoft Azure experienced connectivity issues with its Azure Front Door service across multiple regions. This resulted in latency, timeouts, and errors for client redirection, causing intermittent timeouts and authentication failures for Okta users attempting to authenticate to Microsoft services. Microsoft provides additional details for this disruption under tracking ID: YKYN-BWZ: https://azure.status.microsoft/en-us/status/history/ Remediation Steps: Okta monitored the disruption while Microsoft worked on a resolution. Okta monitoring showed error rates began to decrease at 11:35 AM PDT, and Microsoft confirmed that their services were fully restored at 4:05 PM PDT.

Read the full incident report →

Started Oct 20, 2025, 06:48 AM UTC· resolved Nov 24, 2025, 05:06 PM UTC

1. resolved Oct 20, 2025, 06:48 AM UTC

   At 20/10/2025 00:15 PT, We're currently experiencing technical difficulties for workflows that are related to an issue with an upstream provider. We're working with the vendor and will provide updates in the next 30 minutes

2. resolved Oct 20, 2025, 08:44 AM UTC

   We're currently experiencing service degradation throughout Workflows across all cells. Due to an issue with an upstream provider, Cells OK1 to OK4 and OP1 are currently impacted. We're working with the vendor and will provide updates in the next 30 minutes.

3. resolved Oct 20, 2025, 09:22 AM UTC

   Okta engineers have made service changes to Workflows to mitigate the issues. Flow executions continue to improve. There are other issues that we are still investigating and will attempt to mitigate further for OK1 to OK4 and OP1. We're working with the vendor and will provide updates in the next 30 minutes

4. resolved Oct 20, 2025, 09:42 AM UTC

   We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes

5. resolved Oct 20, 2025, 10:13 AM UTC

   We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes

6. resolved Oct 20, 2025, 10:44 AM UTC

   We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. Workflows processing has been restored across all Cells. Customers should review their flow executions during the outage as they may have to rerun flows that failed during that time. We will provide updates in the next 60 minutes.

7. resolved Oct 20, 2025, 11:51 AM UTC

   We are still seeing significant improvements in our services in Cells OK1 through to OK4 and OP1. Customers may still experience issues with viewing Syslog events in OK1. We will provide updates in the next 60 minutes.

8. resolved Oct 20, 2025, 12:48 PM UTC

   We are continuing to monitor improvements in our services in Cells OK1 through to OK4 and OP1. Customers may still experience issues with viewing Syslog events in OK1. We will provide an update at approximately 9:30 AM PDT.

9. resolved Oct 20, 2025, 04:41 PM UTC

   We are maintaining our focused monitoring effort on Cells OK1 through to OK4 and OP1. Workflows services have recovered in all US Cells and we recommend reviewing existing workflows for consistency around third-party interactions. We are aware that the experience for viewing Syslog events in OK1 has not yet resolved and we are continuing to remediate these issues. We will provide updates in the next 60 minutes.

10. resolved Oct 20, 2025, 06:14 PM UTC

    We are actively working on persisting issues with Syslog delays in OK1. We will provide our next status updates in 120 minutes or earlier as soon as information becomes available.

11. resolved Oct 20, 2025, 07:00 PM UTC

    We are seeing sustained recovery and improved processing speeds in Cell OK1 on Syslog events. which is helping to work through the existing backlog. We’re continuing to monitor the situation closely to ensure this improvement is sustained. We will provide next update in 180 minutes, or sooner if the backlog is fully processed.

12. resolved Oct 20, 2025, 09:09 PM UTC

    Stability in Cell OK1 continues to show consistent improvement. We are still processing the remaining system logs and will provide our next update in 120 minutes.

13. resolved Oct 20, 2025, 11:17 PM UTC

    Okta continues to mitigate and resolve event processing delays in OK1. We have deployed additional resources to improve processing of events to reduce these delays. We are observing improved processing times and will continue to monitor and will update in 120 minutes.

14. resolved Oct 21, 2025, 01:00 AM UTC

    Following the deployment of additional capacity and resources, we've seen steady acceleration in processing rates. We will continue to track this progress and provide another update in the next 120 minutes.

15. resolved Oct 21, 2025, 02:19 AM UTC

    The issue impacting Syslog processing delays in OK1 and the previous Workflow issues have been resolved and the services have been restored. Additional root cause information will be available within 5 business days.

16. resolved Oct 29, 2025, 12:10 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: Okta’s cloud service provider reported errors starting at 11:48 PM PT per their post-incident assessment. Below is the Okta timeline for the impact on our services. Okta Workflows: On October 19th at 11:55 PM PT Okta began receiving alerts regarding Workflows issues occurring in US FL1. During the incident, customers in this cell experienced errors accessing the Workflows UI. Most workflows continued executing normally during this incident, except for those that contained Workflows Table cards, which included create, update, import, or export functionality. Due to latency issues, organizations invoking API endpoint flows encountered timeouts waiting for flows to complete. Actual Impact Time: Sunday 11:55 PM PT - Monday 2:02 AM PT Okta Syslog Event Processing/Log Streaming Delays: On October 20th at 12:23 AM PT, Okta began receiving alerts that systems related to our system log processing were experiencing delays and errors. Okta immediately began to investigate the issue. During the incident, customers in OK1, OK2, OK3, and OK4 experienced delays in event logs and reports. Additionally, the incident impacted Stream and Webhook events, resulting in increased event processing times. OK2, OK3, OK4 Actual Impact Time: Sunday 11:48 PM PT - Monday 3:36 AM PT OK1 Actual Impact Time: Sunday 11:48 PM PT - Monday 6:46 PM PT Okta SMS MFA Processing errors: Some customers may have also seen SMS delivery and retry failures due to errors in downstream third-party telephony providers. Users were able to access the UI and Admins, and were able to log in. Actual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT Actual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT Root Cause Summary: Okta’s cloud service provider experienced system issues that impacted the Okta service. Remediation Steps: Okta Workflows: After reviewing internal alerting and investigating the issue, at 2:02 AM PT, Okta took mitigating actions to bypass the impacted cloud provider services, and Workflows began stabilizing. Okta continued to monitor until approximately 11:49 AM PT by which time functionality had normalized. Okta Syslog Event Processing/Log Streaming Delays: Following a review of internal alerts, Okta began to analyze and address impacted services. At 2:12 AM PT, OK2, OK3, and OK4 were restored to full operation, and Okta Engineering verified the appropriate resolution of the incident. Events began processing and fully recovered in these environments at 3:36 AM PT. While all other cells had recovered, OK1 continued to experience longer system event processing delays. Once the cloud service system was stabilized, Okta was able to scale up the processing. All system log events for OK1 events were processed by 6:46 PM PT. Preventative Actions: Okta is working closely with the cloud service provider to investigate additional mitigations and improve response to these types of incidents. In addition, Okta is looking for opportunities to improve processes to identify and mitigate issues related to cloud service provider issues faster and more efficiently.

Read the full incident report →

Started Oct 15, 2025, 06:30 PM UTC· resolved Nov 24, 2025, 05:09 PM UTC

1. resolved Oct 15, 2025, 06:30 PM UTC

   We are investigating issues with our authentication service that are causing intermittent login problems with OktaVerify. Our initial findings suggest a conflict related to a recently installed third-party patch. Our team is actively working to gather more details, and we will provide updates in the next 30 minutes.

2. resolved Oct 15, 2025, 07:14 PM UTC

   While our third-party provider is actively addressing the issue on their side, you may continue to experience intermittent errors and service unavailability. We are monitoring the situation closely and will send out another update immediately once we receive concrete steps or a timeline for the fix from our third-party provider.

3. resolved Oct 15, 2025, 11:08 PM UTC

   Our third-party provider has confirmed that this is a system-wide issue on their side and has initiated a top-priority escalation to ensure a swift action plan and fix are developed to restore full functionality. We are actively working with our provider and will send a prompt update as soon as we receive more information.

4. resolved Oct 16, 2025, 12:51 AM UTC

   Our third-party provider, Microsoft, has successfully deployed a critical hotfix resolving authentication issues with Okta Fast Pass on Windows 11, and service stability has been confirmed on our end. To fully implement the resolution, impacted customers are required to perform a system restart. While service is restored, we are now engaged in continuous, high-priority communication with the third-party provider to implement and validate a permanent, long-term solution. We will continue to closely monitor the situation and will post any additional information, including any future required user actions, as soon as it becomes available.

5. resolved Oct 16, 2025, 07:18 PM UTC

   We sincerely apologize for the disruption this incident has caused. Our teams have validated that Microsoft's fix, along with rebooting your machine, will successfully resolve the issue and restore full functionality for impacted users. We will share the complete root cause analysis once it is available.

6. resolved Oct 23, 2025, 02:55 AM 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. Timing: Impact started approximately on October 14, 2025 Impact resolved approximately on October 16, 2025, at 12:18 PM PDT Detection: Customers began reporting authentication failures when using Okta FastPass on Windows devices after installing recent Microsoft security patches. Impact: End users on Windows 11 devices who had recently installed a Microsoft security update (KB5066835) were unable to complete their login when using Okta FastPass with phishing resistance enabled. Root Cause: Microsoft released a security update for Windows 11 that unexpectedly interfered with a local communication method on end-user devices. Okta Verify requires this communication method to perform its FastPass phishing-resistant authentication. This conflict prevented Okta services from validating the authentication attempt, resulting in login failures for affected end users. Remediation Steps: On October 15, 2025, at 4:48 PM PDT, Microsoft resolved the issue and confirmed that end-users would need to reboot their computers to fully apply the fix.

Read the full incident report →

Started Sep 24, 2025, 04:00 PM UTC· resolved Oct 31, 2025, 12:54 AM UTC

1. resolved Sep 24, 2025, 04:00 PM UTC

   On September 24, 2025, customers may have experienced increased latency and repeated retries when running Google imports, which led us to recommend pausing all imports via an admin banner. We have confirmed that the disruption was caused by our third-party provider, and the issue has since been fully resolved. There is no active impact, services are operating normally, and no further action is required from customers. We are collaborating with our provider to complete a comprehensive root cause analysis and will provide it here.

2. resolved Oct 31, 2025, 12:54 AM UTC

   Timing: Incident start: September 24, 2025, at 09:00AM PDT Incident resolved: September 24, 2025, at 4:30 PM PDT Detection: On September 24, 2025, Okta monitoring detected a spike in latency impacting the Google Dashboard. Impact: Google Workspace API latency issues led to Okta performance degradation in job processing, and all customers using the Google Workspace API may have experienced latency issues. Root Cause: The Google Workspace API experienced a latency spike, causing delays in Okta job processing. Okta's system terminated outbound requests that did not receive a response within five minutes. During the Google Workspace API latency spike, the maximum expected wait time exceeded ten minutes, leading to connection terminations before results were received. This increased delay caused Okta jobs to back up, impacting our customers. Additionally, Okta's automatic retry mechanism for socket timeouts further compounded these delays. Google acknowledged this API issue and deployed a resolution.

Read the full incident report →

Started Sep 22, 2025, 08:23 PM UTC· resolved Oct 27, 2025, 11:00 PM UTC

1. resolved Sep 22, 2025, 08:23 PM UTC

   Since September 22, 2025, the Okta Workflows Google Sheets connector has been intermittently returning 'Invalid Input' errors and/or exhibiting unexpected behavior on the New Row event and the Create Row, Read Row, and Read All Rows actions. Other cards may also be impacted. Our teams are actively investigating the root cause and working on a resolution with our third-party provider. We will provide an update as soon as more information is available.

2. resolved Oct 09, 2025, 10:54 PM UTC

   We appreciate your patience while we addressed this issue. The service has shown stability since October 7th, and following an extended period of monitoring, we can now confirm that the issue is fully resolved. We are working with our provider on a thorough Root Cause Analysis (RCA), which we will post here.

3. resolved Oct 27, 2025, 11:00 PM UTC

   Timing: Incident start: September 22, 2025, at 2:25 PM PDT Incident resolved: October 3, 2025, at 5:00 PM PDT Detection: On September 22, 2025, Okta customers began reporting intermittent errors with specific Google Sheets connector functions in Okta Workflows. Impact: Okta customers utilizing Okta Workflows could experience runtime errors for several Google Sheets connector cards, including Read Row, Read All Rows, Clear Row, and New Row. These actions failed intermittently, returning errors such as: - 500 - Invalid Input: Invalid input for 'list'. Expected a list. - ScriptError 400 - Invalid input for "keys". Root Cause: The intermittent failures stemmed from a remediation step taken for a separate, preceding disruption (I-9545) involving the Google Sheets connector. Following that incident, Okta teams implemented a configuration change to the connector based on feedback from Google. While this change resolved the initial issue, it inadvertently introduced a new, intermittent condition. This change caused some customer requests to be incorrectly routed to a stale, cached version of the connector’s implementation within Google infrastructure. This cached version of the implementation did not contain more recent updates, which led to the intermittent failures experienced by customers. Remediation Steps: Okta Engineering worked with Google to investigate the new behavior. Once the root cause was identified, Okta Engineering developed and tested an updated configuration for the Google Sheets connector. This fix was then deployed progressively across all preview and production environments, with service stability and error-rate monitoring confirmed at each stage. This culminated in a complete resolution of preview and commercial environments on October 3, 2025. Preventive Actions: Okta has updated its internal operational procedures for this connector to prevent recurrence. Runbooks have been revised to include this scenario and prioritize alternative recovery steps to ensure greater service resilience.

Read the full incident report →

Started Sep 22, 2025, 06:21 PM UTC· resolved Oct 23, 2025, 02:52 AM UTC

1. resolved Sep 22, 2025, 06:21 PM UTC

   We have identified an issue with the Google Groups Query API, which is returning inconsistent or incomplete group data. This transient API issue can result in unintended group deletion of those groups in Okta. As a workaround, we have implemented a protective measure to prevent accidental deletion during group imports from Google. When a large volume of group deletions is detected, the import is stopped to protect against importing bad data. Customers with a verified, legitimate need for a mass deletion can contact Support to enable a temporary override for this limit. Our team is collaborating with our third-party provider to implement a permanent fix, and a Root Cause Analysis will be forthcoming.

2. resolved Oct 23, 2025, 02:52 AM UTC

   Incident start: September 15, 2025 Incident resolved: September 25, 2025 Detection: Okta was alerted to the issue after customers reported that groups managed by Google Workspace were being unexpectedly removed from Okta during the import process. Impact: Customers utilizing the Google Workspace integration may have experienced the following during this period: During scheduled or manual imports, groups (which still existed in Google Workspace) were unexpectedly removed from Okta. The unintended removal of groups may have resulted in a loss of application access for users who were members of the affected groups. Root Cause: The root cause was an issue within the Google Workspace Directory API, which Okta services rely on for group imports. The API intermittently returned incomplete lists of groups without correctly indicating that the data was partial. This led Okta services to interpret the incomplete data as the complete list of groups. As a result, any groups not included in the incomplete API response were processed as if they had been intentionally deleted in Google Workspace, leading to their removal within Okta as part of the import. Google acknowledged this API issue and deployed a resolution on or around September 25, 2025. Remediation Steps: Okta advised customers to pause all Google group imports until the third-party provider resolved the underlying issue. Preventive Actions: Okta Engineering implemented a proactive measure to automatically halt Google group imports when a large number of deletions is detected. This safeguard was put in place to avoid processing incomplete data and further unintended group removals. Further, Okta teams worked with Google as they worked to identify and resolve the underlying API issue.

Read the full incident report →

Started Sep 22, 2025, 12:30 PM UTC· resolved Oct 07, 2025, 11:28 PM UTC

1. resolved Sep 22, 2025, 12:30 PM UTC

   At 9/22/2025 5:30 AM PT, the Workflows Automation and Extensibility team became aware of an issue with connectivity to our Workflows service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, US Preview 1, EMEA Preview 2, US Preview 3, EMEA Cell 1. Our team is actively investigating this issue and performing configurational changes to mitigate the issue. We will provide another update within the next 1 hour, or sooner if additional information becomes available. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Sep 22, 2025, 01:59 PM UTC

   Okta Engineering is actively working to identify the root cause of a Google Sheet connector issue that may cause customers to experience 404 errors when using certain workflow cards. As additional information becomes available, we will provide another update in approximately 60 minutes or sooner.

3. resolved Sep 22, 2025, 02:58 PM UTC

   The Workflows Automation and Extensibility team is continuing to work on the issue, and multiple mitigation efforts are underway. We will provide updates in the next 60 minutes.

4. resolved Sep 22, 2025, 04:09 PM UTC

   Our teams are working with our third-party provider to address the underlying issue. We have no estimated time for a full resolution, but we are committed to providing timely updates within the next 60 minutes.

5. resolved Sep 22, 2025, 05:08 PM UTC

   We are working closely with our third-party provider to address the ongoing issue of our Google Sheets connector cards returning 404 errors when used with Apps Script. We are jointly developing a clear path to resolution and actively monitoring the progress. An update will be provided within the next 60 minutes.

6. resolved Sep 22, 2025, 06:04 PM UTC

   We are fully engaged with our third-party provider as this service degradation continues due to an external dependency. You may continue to experience 404 errors until the root cause is addressed. We appreciate your patience and will share more on our progress in 60 minutes.

7. resolved Sep 22, 2025, 07:08 PM UTC

   The service degradation affecting Google Sheets is still ongoing. The issue requires close collaboration with our third-party provider to ensure any changes we make do not interfere with their work and impact other services. We will provide our next update in 60 minutes.

8. resolved Sep 22, 2025, 08:29 PM UTC

   A fix for the Google Sheets connection has been tested and confirmed. It resolves the previous 404 runtime errors without requiring customers to re-authenticate. The next steps include test deployment to verify its compatibility with existing connections. We will share another update within 60 minutes.

9. resolved Sep 22, 2025, 09:24 PM UTC

   Our engineering team is continuing to test and monitor the fix in the Preview environment. Once we have confirmed its stability, we will fully deploy it to our production environment. We will share our next update in 60 minutes.

10. resolved Sep 22, 2025, 10:00 PM UTC

    Our Engineering team has successfully deployed a fix to all impacted environments and is now actively monitoring its performance. We appreciate your continued patience and will provide a final update in 30 minutes.

11. resolved Sep 22, 2025, 10:28 PM UTC

    The issue that affected Google Sheets has been resolved, and services have been restored. Additional root cause information will be available within 5 Business days.

12. resolved Oct 07, 2025, 12:06 AM 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 are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On September 22nd at 2:12 am PST, Okta was alerted to an issue where some customers executing flows with Google Sheets connectors saw 404 error messages. Root Cause Summary: A change made by the third-party provider resulted in a 404 error message on the Google Sheets workflows connector. Remediation Steps: Okta began diagnosing the issue and engaging with the third party support team immediately upon receiving reports of the error. Following the investigation, the Okta team implemented a fix which resulted in the restoration of Google sheets connector functionality. Preventative Actions: Okta is reviewing and enhancing monitoring and alerting processes to minimize impacts to customers for similar issues in the future.

Read the full incident report →

Started Aug 18, 2025, 11:06 AM UTC· resolved Aug 25, 2025, 08:39 PM UTC

1. resolved Aug 18, 2025, 11:06 AM UTC

   At 8/18/2025 5:00 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting some customers. 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 30 minutes, or sooner if additional information becomes available.

2. resolved Aug 18, 2025, 03:52 PM UTC

   Okta Engineering is continuing to investigate service disruptions. During this time, users using certain ISP providers may experience connection timeouts when attempting to reach Okta domains. Customers can try connecting via a mobile hotspot or an alternative network provider, which may allow those users to reach Okta domains. We will provide another update in approximately 30 minutes, or sooner if additional information becomes available.

3. resolved Aug 18, 2025, 04:32 PM UTC

   Okta Engineering is continuing to investigate service disruptions. During this time, users using certain ISP providers may experience connection timeouts when attempting to reach Okta domains. Customers can try connecting via a mobile hotspot or an alternative network provider, which may allow those users to reach Okta domains. We will provide another update in approximately 60 minutes, or sooner if additional information becomes available.

4. resolved Aug 18, 2025, 05:33 PM UTC

   Our investigation has confirmed that the Okta platform is operating as expected. We are continuing to monitor an external issue where users on certain ISPs may experience connection timeouts when accessing some Okta domains. Affected users can try connecting via a mobile hotspot or an alternative network provider as a potential workaround. We are actively engaged with our external partners to help facilitate a resolution. We will provide another update in approximately 60 minutes, or sooner if new information becomes available.

5. resolved Aug 18, 2025, 06:33 PM UTC

   The ISP connectivity issue affecting some customers is confirmed to be resolved. Additional root cause information will be available within 5 business days.

6. resolved Aug 25, 2025, 08:37 PM UTC

   The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted users using Okta services. Timing: Incident start: August 18, 2025, at 4:06 AM PDT Incident resolved: August 18, 2025, at 11:29 AM PDT Detection: Customers began reporting that their organization's page was unreachable for certain users. Impact: A subset of customers experienced an "ERR_CONNECTION_TIMED_OUT" error when attempting to access their Okta organizations, which prevented them from logging in. Root Cause: A third-party Internet Service Provider experienced an issue that impaired network traffic from their infrastructure to certain other services, including those provided by Okta. This disruption primarily impacted connectivity for Google Fiber customers in the Texas region, though other providers and locations may have also been affected. The third-party provider later resolved this issue.

Read the full incident report →

Started Aug 08, 2025, 09:28 AM UTC· resolved Aug 20, 2025, 11:29 PM UTC

1. resolved Aug 08, 2025, 09:28 AM UTC

   An issue impacting third party provider(s) regarding import slowness has been resolved. Additional root cause information will be available within 5 business days. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16

2. resolved Aug 20, 2025, 11:29 PM UTC

   The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted the Okta service. Timing: Incident start: August 7, at 06:02 PM PDT Incident resolved: August 8, at 02:00PM PT Detection: Okta Engineering was alerted to backend jobs queues increasing due to a slow third-party provider API response. Impact: Customers may have seen slow job processing in Okta. Summary: Jobs were queued due to job execution times increase while waiting for third-party provider API responses. Our third-Party provider has identified a configuration error and resolved this issue by provisioning additional resources to these APIs. Preventive Actions: Okta has introduced additional logging to identify similar disruptions closer to their start.

Read the full incident report →

Started Aug 01, 2025, 02:29 PM UTC· resolved Aug 11, 2025, 08:13 PM UTC

1. resolved Aug 01, 2025, 02:29 PM UTC

   At 8/1/2025 7:29 AM PT, the Workflows Automation and Extensibility team became aware of an issue with timeouts to our service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, US Cell 11. 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 30 minutes, or sooner if additional information becomes available. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11, okta.com:14

2. resolved Aug 01, 2025, 03:49 PM UTC

   The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. During this time, workflows may be delayed or timeout. The Workflows Automation and Extensibility team has applied some changes to mitigate the issue and is monitoring for improvements. We'll provide an update in 30 minutes, or sooner, as additional information becomes available.

3. resolved Aug 01, 2025, 04:14 PM UTC

   The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. During this time, real-time flows are delayed and may time out. Non-real-time flows are now running with normal latency. The Workflows Automation and Extensibility team is applying further mitigations to the issue and monitoring for improvements. We'll provide an update in 30 minutes, or sooner, as additional information becomes available.

4. resolved Aug 01, 2025, 04:53 PM UTC

   The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. During this time, real-time flows are delayed and may time out. Non-real-time flows are now running with normal latency. The Workflows Automation and Extensibility team is continuing to apply further mitigations to the issue and monitoring for improvements. We'll provide an update in 1 hour, or sooner, as additional information becomes available.

5. resolved Aug 01, 2025, 06:01 PM UTC

   The Workflows Automation and Extensibility team is still monitoring the fix applied to address the incident impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. Mitigation is progressing, and customers should be seeing fewer delays or timeouts. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.

6. resolved Aug 01, 2025, 06:57 PM UTC

   The Workflows Automation and Extensibility team continues to monitor the fix applied to address the incident impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. Workflow services should be processing normally at this time. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.

7. resolved Aug 01, 2025, 08:09 PM UTC

   The Workflows Automation and Extensibility team continues to observe steady recovery in the Workflow services that impacted US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.

8. resolved Aug 01, 2025, 09:21 PM UTC

   The team is continuing to monitor the fix implemented to resolve the recent Workflows incident. While we're seeing clear indications of recovery, we're proceeding with an abundance of caution to ensure full stability. Customer workflows should be seeing improvements, and we're working diligently to ensure everything flows smoothly. We'll share our next update in 120 minutes.

9. resolved Aug 01, 2025, 11:22 PM UTC

   The initial impact has fully recovered on OK14, and we're transitioning from active response to a dedicated monitoring phase on the other cells. Our engineers are continuously tracking system performance to ensure full stability. While we expect services to remain stable, if you experience any Workflow-related errors, please contact our support team for assistance.

10. resolved Aug 02, 2025, 03:46 AM UTC

    The Workflow issues for US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, US Cell 11, and US Cell 14 have been addressed. Our monitoring shows a return to normal conditions. Our team is collaborating with our third-party vendor to identify the underlying root cause, and a Root Cause Analysis will be forthcoming.

11. resolved Aug 11, 2025, 08:13 PM UTC

    We sincerely apologize for any impact this incident has caused you, your business, and your customers. At Okta, trust and transparency are our top priorities. The facts regarding this incident are outlined below. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On Friday, August 1st, at 4:13 AM PT, Okta was alerted to an issue in which message brokers were quickly exhausting disk space and causing delayed workflow processing in Cells OK1, OK2, OK3, OK4, OK6, OK7, OK11, and OK14. Starting at approximately 5:00 AM PT, users may have experienced processing delays, API timeouts, or Workflow executions ending prematurely with internal server errors. Delayed Workflow executions that were rerouted to healthy infrastructure were processed successfully. Root Cause Summary: Based on our investigation and findings, the root cause of this issue was a disk space leak caused by a duplicate session within services managed by a third-party operator introduced during a maintenance window. Remediation Steps: Immediately upon receiving alerts of service disruptions, Okta Engineering escalated the issues with our provider and worked to implement internal mitigations. While troubleshooting the issue, Okta brought up multiple additional message brokers and swapped them as needed to balance the various waves of requests. Okta's internal mitigations restored service to the affected cells by approximately 12:34 PM PT, with additional stabilization work continuing through the afternoon. Okta continued to work directly with our provider to mitigate the issue and confirmed complete service restoration throughout the weekend. Preventative Actions: Okta will continue working with our third-party service provider to enhance monitoring and communication, expedite detection, and improve processes for making infrastructure changes. Additionally, we are updating our operational procedures for scaling clusters and connections to improve service recovery times further. Duration (# of minutes): 454

Read the full incident report →

Started Jul 22, 2025, 06:00 PM UTC· resolved Jul 30, 2025, 12:03 AM UTC

1. resolved Jul 22, 2025, 06:00 PM UTC

   At 7/22/2025 11:30 AM PT, the Core Identity team became aware of an issue with authentication to our Core Platform service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, US Preview 1, EMEA Preview 2, US Preview 3, EMEA Cell 1. During this time, admins may notice some users that should be auto-activated stuck in 'Pending User Action' status. Our team is actively investigating this issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Jul 22, 2025, 07:25 PM UTC

   Okta has reproduced the issue and is currently working on a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.

3. resolved Jul 22, 2025, 07:54 PM UTC

   Okta has reproduced the auto-activation issue and is continuing to work toward a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.

4. resolved Jul 22, 2025, 08:37 PM UTC

   Okta has resolved the auto-activation issue and import functionality was fully restored at 1:37 PM PST. Additional root cause information will be available within 5 business days.

5. resolved Jul 30, 2025, 12:03 AM 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 the service to prevent future occurrences of this incident. Detection and Impact: On July 22nd, Okta triggered incident processes investigating issues affecting automatic user activation from API and Directory Imports across all production cells. Users were erroneously left in a pending state despite the update appearing as completed. Root Cause Summary: Okta Engineering determined that the root cause of the issue originated from an update deployed on 7:56 PM (PT) July 9th, which, due to a behavior change that mishandled user states, could result in some newly provisioned users being left in a pending state. Remediation Steps: Once the source of the issue was identified, Okta engineering rolled back changes at 12:11 PM (PT) on July 22nd. These actions successfully addressed the issue and restored normal operations by 1:29 PM (PT). Preventative Actions: To prevent future incidents, Okta is adding additional test cases and improving processes to better the resiliency of user auto provisioning processes. In addition, we are reviewing our internal processes to assimilate issues and expedite escalations to improve our time to resolve these types of issues. Total Duration: Total Duration (Minutes): 12 days 17 hrs 32min Actual Time: 7/9/2025 7:56:04PM - 7/22/2025 1:29:03PM Duration (# of minutes): Total Duration (Minutes): 17,280 mins

Read the full incident report →

Started Jun 12, 2025, 05:50 PM UTC· resolved Jun 25, 2025, 08:09 PM UTC

1. resolved Jun 12, 2025, 05:50 PM UTC

   Android Okta Verify end-users may not receive push notifications due to a third-party outage. Launching Android Okta Verify manually will allow authentication. Okta will provide an update as it becomes available. Affected cells: okta.com:6, okta.com:9, okta.com:11

2. resolved Jun 12, 2025, 08:06 PM UTC

   Okta monitoring shows push notifications on Android Okta Verify due to a third-party outage have recovered. Additional root cause information will be available within 10 Business days.

3. resolved Jun 25, 2025, 08:07 PM UTC

   The following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. Timing: Incident start: June 12, 2025, 10:50 AM PT Incident resolved: June 12, 2025, 12:15 PM PT Detection: Okta Engineering noticed errors related to this feature on June 12, 2025. Impact: During this outage, Android users attempting to authenticate via Push would not receive a push notification on their device and would be required to open Okta Verify to complete authentication. Summary: Google Cloud Services confirmed disruptions to their services (including those necessary for the delivery of Android push notifications) that were resolved on June 12, 2025, at 13:49 PT. More details, as provided by Google, can be found here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW.

Read the full incident report →

Started Jun 12, 2025, 01:09 AM UTC· resolved Jun 18, 2025, 10:42 PM UTC

1. resolved Jun 12, 2025, 01:09 AM UTC

   At 6:09 PM PST on June 11, 2025, Okta became aware of an issue with our service affecting customers in US Cell 6, APAC Cell 8. This issue has been resolved. Okta took corrective action to resolve the service interruption. The service was fully restored at 6:23 PM PST. Additional root cause information will be available within 5 Business days. Affected cells: okta.com:6, okta.com:8

2. resolved Jun 18, 2025, 10:40 PM 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 the service to prevent future occurrences of this incident. Detection and Impact: On June 11th at 6:07 PM PT, Okta internal monitoring alerted responders regarding a database issue across cells US Cell 6 and APAC Cell 1. Primary databases were deadlocking, resulting in the cell switching to [read only] (https://support.okta.com/help/s/article/What-is-Oktas-Readonly-Mode?language=en_US) mode. During this time, users in Cells US Cell 6 and APAC Cell 1 would have encountered read only mode during this period. Root Cause Summary: Okta had progressively rolled out a configuration change earlier in the day as part of normal scheduled operations. This change exposed an error case which was then observed only in specific environments. Okta determined that MySQL contained a bug which, when a new specific monitoring query was executed, resulted in deadlocking the replica database servers and blocking additional queries from being executed. Okta managed the issue by executing database recovery efforts, thus restoring functionality and availability to normal operating levels. Cleanup procedures for this issue, which entailed rollback of the previously executed configuration change, were executed later in the day in a staggered fashion. During this process, the database primaries for US Cell 6 and APAC Cell 1 unexpectedly experienced a similar deadlock issue. Remediation Steps: During this period US Cell 6 and APAC Cell 1 switched into Read Only mode. Okta engineers executed database failover and recovery operations to return the cell to normal operation. Impact Durations: US Cell 6 - 6:06 PM PT - 6:18 PM - 12 minutes APAC Cell 1 - 6:06 PM PT - 6:24 PM - 18 minutes At 6:24 PM PT all servers had recovered and had returned to normal operations. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: Review of database rollback process utilized between replicas and primaries Review sequencing of database configuration updates deployed across environments. These learnings work to prevent similar incidents from happening again.

Read the full incident report →

Started Jun 11, 2025, 06:05 PM UTC· resolved Jun 16, 2025, 09:33 PM UTC

1. resolved Jun 11, 2025, 06:05 PM UTC

   We have identified an issue with Okta Personal where end users are unable use the application

2. resolved Jun 11, 2025, 06:16 PM UTC

   Engineering has identified and resolved an issue where end users are unable to access Okta Personal vault due to a failed DB migration. End user data was unaffected.

3. resolved Jun 16, 2025, 09:33 PM UTC

   Out of an abundance of caution, an update was posted at 11:05 am PDT on June 11, 2025. However following additional investigation, it was determined that a broad service degradation / disruption notice was not applicable. Okta will continue to monitor closely and directly engage with any customers as needed.”

Read the full incident report →