Duo Security Outage History

Started Dec 19, 2025, 05:59 PM UTC· resolved Dec 19, 2025, 09:03 PM UTC

1. investigating Dec 19, 2025, 05:59 PM UTC

   We are currently investigating an issue causing new Duo Trial signups to fail. We are working to restore this capability as soon as possible and will provide additional updates here as progress is made. Please check back here or subscribe to updates for any changes.

2. identified Dec 19, 2025, 07:12 PM UTC

   We have identified the cause of the issue affecting Duo trial signups and are actively working on a fix. Additional updates will be shared as progress is made.

3. monitoring Dec 19, 2025, 08:24 PM UTC

   We have deployed a fix for the issue causing Duo Trial signups to fail and are monitoring the results of the fix at this time.

4. resolved Dec 19, 2025, 09:03 PM UTC

   The issue affecting Duo Trial signups has been resolved.

Read the full incident report →

Started Oct 20, 2025, 08:28 AM UTC· resolved Oct 20, 2025, 11:06 AM UTC

1. investigating Oct 20, 2025, 08:29 AM UTC

   We are currently investigating an issue causing phone call and SMS delivery authentication failures on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

2. identified Oct 20, 2025, 08:52 AM UTC

   We've identified the cause of degraded Phone Authentication and SMS delivery failures. Our providers have acknowledged an upstream issue and are working on a resolution. This may affect users relying on phone calls or SMS for authentication across all deployments and we suggest using alternate means of MFA such as Duo Push if possible. Our team is working on mitigation steps and will continue to provide updates as progress is made.

3. resolved Oct 20, 2025, 11:06 AM UTC

   The issue affecting phone-based authentication and SMS delivery has now been resolved. System performance has remained stable, and all services are operating as expected across deployments. We will continue to monitor for any anomalies, but no further impact is anticipated at this time.

Read the full incident report →

Started Oct 20, 2025, 07:54 AM UTC· resolved Oct 20, 2025, 11:20 AM UTC

1. investigating Oct 20, 2025, 07:54 AM UTC

   We are currently investigating an issue affecting email delivery. Our team is working to identify the root cause and restore full functionality as quickly as possible. We'll provide updates as soon as more information becomes available. Authentication is not impacted. Thank you for your patience.

2. identified Oct 20, 2025, 09:44 AM UTC

   We have identified the cause of the issue with email delivery with the Duo Admin Panel and are actively working to restore service.

3. resolved Oct 20, 2025, 11:20 AM UTC

   The issue affecting email delivery has been resolved. System performance has remained stable, and all services are functioning normally across deployments. We’ll continue to monitor to ensure ongoing reliability. Thank you for your patience throughout this incident.

Read the full incident report →

Started Oct 15, 2025, 12:19 PM UTC· resolved Oct 15, 2025, 08:01 PM UTC

1. investigating Oct 15, 2025, 12:19 PM UTC

   We are currently investigating an issue causing Duo Desktop to not be recognized during authentications on Windows 11 24H2/25H2. If possible, please refrain from upgrading to 24H2/25H2 at this time. However, if this has already been done, downgrading to the previous version will resolve the issue. Please check back here or subscribe to updates for any changes.

2. identified Oct 15, 2025, 04:00 PM UTC

   We have identified an issue with a recent Windows update that has caused Duo Desktop to not be recognized on Windows 11 24H2 and 25H2 and have some recommended remediation steps to resolve the issue. We have published a KB article with the steps: https://help.duo.com/s/article/9527 We are working with Microsoft to provide a more permanent solution in a future Windows update. Please check back here or subscribe to updates for any changes.

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

   We have identified an issue with a recent Windows update that has caused Duo Desktop to not be recognized on Windows 11 24H2 and 25H2 and have provided remediation steps in a Knowledge Base article linked below. While we work with Microsoft to ensure a permanent solution is provided via update, we will be marking this incident resolved and providing further updates through the KB article as well as via email communications. Why is Duo Desktop not detected on my Windows device after installing updates to Windows 11? https://help.duo.com/s/article/9527 Please check the KB article for any further updates.

Read the full incident report →

Started Oct 07, 2025, 07:13 PM UTC· resolved Oct 07, 2025, 07:56 PM UTC

1. investigating Oct 07, 2025, 07:13 PM UTC

   We are currently investigating an issue causing a full outage for all services on our DUO34 deployment and are working to restore services as soon as possible. Please check back here or subscribe to updates for any changes

2. identified Oct 07, 2025, 07:23 PM UTC

   We have identified the issue causing an outage for all services on our DUO34 deployment and working to deploy a fix.

3. monitoring Oct 07, 2025, 07:44 PM UTC

   We have deployed a fix for the issue causing an outage for all services on our DUO34 deployment and are monitoring the results at this time.

4. resolved Oct 07, 2025, 07:56 PM UTC

   The issue causing an outage for all services on our DUO34 deployment has been resolved. We will publish a RCA as soon as it is available. You can check back here for the latest information or subscribe for updates.

5. postmortem Oct 09, 2025, 02:04 PM UTC

   # **DUO34 Deployment Outage** ## Incident Report – 10/7/2025 ### Summary On October 7, 2025, between 2:40pm EDT and 3:40pm EDT, all services on Duo 34 were unavailable. This was due to a misconfiguration in our edge load balancer which stopped all traffic to that deployment. Duo engineering promptly fixed the misconfiguration and have fixed the underlying cause, to ensure our systems are more resilient. ### Details Duo’s application platform has two parts to manage our services. One-part handles creating the network setup, and the other controls how traffic reaches running services. A service disruption occurred because of a misalignment between these two key systems. Even though the network was set up correctly, changes were not reflected in the traffic routing settings. This caused traffic to stop reaching the services, resulting in the outage. To restore service, a manual fix was put in place to connect these network servers with the right settings. As a long-term solution, we have updated the system settings to point to the right destinations. This will ensure that the misalignment will not happen again. To avoid this problem in the future, we're reviewing how we manage system configurations, improving our setup process to avoid local files, and adding checks to stop changes that could cause similar issues.

Read the full incident report →

Started Sep 29, 2025, 09:46 AM UTC· resolved Sep 29, 2025, 04:52 PM UTC

1. investigating Sep 29, 2025, 09:46 AM UTC

   We are current investigating issue where custom attributes are not being synced from Entra ID to Duo. Entra ID sync is working as expected with standard attributes. Please refer to the status page for further updates.

2. investigating Sep 29, 2025, 10:32 AM UTC

   We are continuing to investigate this. Please pause your Entra ID sync if you are using any custom attributes as sync attributes, and, if possible, do not run a full manual sync until the issue is resolved. As a workaround, an admin can sync individual users by following the instructions in our guide below: https://duo.com/docs/azuresync#sync-individual-users-from-the-duo-admin-panel

3. identified Sep 29, 2025, 04:16 PM UTC

   We have identified the issue causing custom attributes to not sync from Entra ID to Duo and are working with the vendor to resolve it. We will work with affected customers while a fix is developed and deployed. Please reach out to [email protected] or give us a call at the number listed for your region on our Support Page, https://duo.com/support. We will close this incident on the Status Page shortly. Please pause your Entra ID sync if you are using any custom attributes as sync attributes, and, if possible, do not run a full manual sync until the issue is resolved. As a workaround, an administrator can sync individual users by following the instructions in our guide below: https://duo.com/docs/azuresync#sync-individual-users-from-the-duo-admin-panel

4. resolved Sep 29, 2025, 04:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 26, 2025, 02:54 PM UTC· resolved Sep 26, 2025, 10:41 PM UTC

1. identified Sep 26, 2025, 02:54 PM UTC

   We have identified an issue preventing administrators from accessing the Duo AI Assistant for the first time and are working to deploy a fix. Administrators who have previously used the AI Assistant are unaffected. Please check back here or subscribe to updates for any changes.

2. monitoring Sep 26, 2025, 09:42 PM UTC

   A known fix has been implemented, and we have seen a restoration of service. We will continue to actively monitor the results to ensure the issue is fully resolved.

3. resolved Sep 26, 2025, 10:41 PM UTC

   We have confirmed the issue is now fully resolved. An RCA will be provided as soon as it is available.

Read the full incident report →

Started Sep 09, 2025, 04:43 PM UTC· resolved Sep 09, 2025, 05:09 PM UTC

1. identified Sep 09, 2025, 04:44 PM UTC

   We have identified an issue causing login failures on cross deployment logins to the Duo Admin Panel on multiple deployments. We are working to correct the issue as soon as possible.

2. monitoring Sep 09, 2025, 04:54 PM UTC

   A fix has been deployed for the issue causing login failures on cross deployment logins to the Duo Admin Panel and we are monitoring the results.

3. resolved Sep 09, 2025, 05:09 PM UTC

   The issue regarding login failures on cross deployment logins to the Duo Admin Panel has been resolved and functionality has been fully restored. An RCA will be provided as soon as it is available.

4. postmortem Sep 10, 2025, 09:27 PM UTC

   ### Summary On September 9, 2025, between approximately 12:10 pm ET and 12:40 pm ET, some multi-tenant administrators were unable to access the admin panel or use accounts API due to a configuration change that inadvertently disrupted traffic requests. Duo engineering promptly reverted the change to restore service and resolve the issue. ### Details On September 9, Duo engineering executed a planned integration of two services related to the admin panel and billing. This integration aimed to reduce database load and address infrequent internal errors. Although the change was tested in lower environments, it was incompatible with the production region it targeted, causing issues when deployed in production. Duo engineering promptly began reverting the change to address the errors and minimize customer impact. On the same day, the team implemented a fix to resolve the configuration incompatibilities. Moving forward, Duo is enhancing our testing processes to identify incompatibilities before implementing approved changes and to reduce downtime for our customers. We apologize for any disruption this may have caused.

Read the full incident report →

Started Aug 29, 2025, 05:30 PM UTC· resolved Aug 30, 2025, 05:03 AM UTC

1. identified Aug 29, 2025, 05:30 PM UTC

   We are currently aware of an issue that is impacting users logging into web-based applications from both Chrome and Edge version 136 that causes a blank Duo Prompt to appear. We are working on a fix for this issue urgently and hope to provide an update soon. As a workaround, if users upgrade their browser to a newer version, authentication will work as normal, which is also a recommended best practice for security as well. Additionally, users logging into Epic Hyperdrive may also experience this issue when attempting to log in, and our fix will also apply to that application once released. As a temporary workaround, you can downgrade Hyperdrive to 100.2506.3, which will move to a lower Chromium Version (134.0.6998.205) and no longer see the issue. As soon as our fix has been released, we'll provide an update as soon as possible.

2. monitoring Aug 30, 2025, 04:05 AM UTC

   A fix has been deployed for the blank prompt issue affecting Chrome/Edge version 136. We are monitoring the results of the fix at this time. Please check back here or subscribe to updates for any changes.

3. resolved Aug 30, 2025, 05:03 AM UTC

   The issue causing the blank prompt is now resolved and full functionality is restored. We will be posting a root-cause analysis (RCA) here once our engineering team has finished its thorough investigation of the issue.

4. postmortem Sep 03, 2025, 03:10 PM UTC

   ### Summary An apparent defect in v136 of Chromium-based browsers \(such as Google Chrome and Microsoft Edge\) caused newly added code in Duo’s web-based prompt, when interacting with Duo Desktop, to freeze or crash the browser tab. The issue was specific to version 136; all other versions did not exhibit the problem. Duo has deployed a fix to ensure this behavior is not present in these versions. ### Timeline of Events * 8/29/2025 1:25am EST - Duo engineering is alerted of a customer reporting the issue * 8/29/2025 1:22pm EST - Incident created * 8/29/2025 9:35pm EST - Started deploying the update to fix the issue * 8/29/2025 11:36pm EST - Finished deploying the update to fix the issue * 8/30/2025 12:07am EST - Status page is updated to monitoring * 8/30/2025 1:02am EST - Status page is updated to resolved ### Details Updates were added to D322 to check whether the Chrome Local Network Access permission setting was enabled in the browser being used to authenticate. The Local Network Access permission is being added to Chromium-based browsers in v141, and changes were added to improve the user experience if the Local Network Access permission is not enabled. More details can be found in [this Duo Knowledge Base article](https://help.duo.com/s/article/9470?language=en_US). In v136 of Chromium-based browsers, the change that was added to check the Local Network Access permission caused the browser to freeze or crash. To resolve this issue, Duo added a change to not check the Chrome Local Network Access permission if v136 of a Chromium based browser is being used. Since the Chrome Local Network Access permission is being released in v141, this change did not have any negative impact. Duo will explore adding additional testing and alerting for issues like this one, where only specific browser versions are impacted by an issue.

Read the full incident report →

Started Aug 26, 2025, 02:43 PM UTC· resolved Aug 26, 2025, 02:58 PM UTC

1. investigating Aug 26, 2025, 02:43 PM UTC

   We are currently investigating an issue affecting updates or changes made to users in the Admin Panel on selected deployments. Please check back here or subscribe to updates for any changes.

2. monitoring Aug 26, 2025, 02:48 PM UTC

   A fix has been deployed for the issue affecting updates or changes made to users in the Admin Panel on selected deployments. We are monitoring the results of the fix at this time. Please check back here or subscribe to updates for any changes.

3. resolved Aug 26, 2025, 02:58 PM UTC

   The issue affecting updates or changes made to users in the Admin Panel on selected deployments has been resolved.

Read the full incident report →

Started Aug 26, 2025, 08:08 AM UTC· resolved Aug 26, 2025, 11:43 AM UTC

1. investigating Aug 26, 2025, 08:08 AM UTC

   We are currently investigating an issue impacting user management and Active Directory sync on selected deployments. Please refer to the status page for further updates.

2. investigating Aug 26, 2025, 08:09 AM UTC

   We are continuing to investigate this issue.

3. identified Aug 26, 2025, 09:06 AM UTC

   A fix has been deployed for the issue affecting User Management and SSO logins on Duo3, Duo47, and Duo57. We are monitoring performance and stability. Please refer to the status page for further updates.

4. monitoring Aug 26, 2025, 09:29 AM UTC

   Following the implementation of the fix, we are seeing signs of recovery. We will continue to actively monitor the results to ensure the issue is fully resolved. Please refer to the status page for further updates.

5. resolved Aug 26, 2025, 11:43 AM UTC

   The issue affecting User Management and SSO logins on Duo3, Duo47, and Duo57 has been fully resolved, and all services have been restored to normal functionality. We will publish a RCA as soon as it is available. You can check back here for the latest information or subscribe for updates.

6. postmortem Aug 29, 2025, 06:50 PM UTC

   **Summary** A change in the D322 build triggered high database load by calling an unoptimized query. This resulted in disruptions across several deployments. The system was stabilized after recovery actions. **Timeline of Events** 08/26/2025 06:47:00 UTC - Alert fires that our service latency is above target. 08/26/2025 06:58:00 UTC - On-call engineer confirms that autoscaling is in progress. 08/26/2025 07:00:00 UTC - Separate alert fires that our service database CPU utilization is high, and requests backlog starts to grow. 08/26/2025 07:37:00 UTC - On-call engineer disables certain features of our service to alleviate load. 08/26/2025 08:08:00 UTC - Status page is published. 08/26/2025 08:45:00 UTC - Service database is scaled up. 08/26/2025 08:50:00 UTC - On-call engineer monitors recovery of systems. 08/26/2025 10:40:00 UTC - All features of our service are reenabled. 08/26/2025 11:44:00 UTC - Status page is updated to resolved. **Details** Our D322 build started calling an unoptimized API endpoint on an internal system which led to high database load, latency and request timeouts. This degraded multiple deployments \(DUO3, DUO47, DUO57\). ‌ To alleviate load, certain features were disabled temporarily. However, because Duo Directory depends on this feature, customers received errors until it was re-enabled. At the same time, the database was scaled up vertically to allow for quicker processing of backlogged requests. ‌ Once the backlog was cleared, all features were reenabled and the incident was resolved. ‌ Deep analysis was conducted to determine why the service database CPU utilization was higher than expected. A newly introduced unoptimized query was found and fixed promptly. ‌ Furthermore, our teams have plans to implement more rigorous testing and review processes for new database queries that are added to our services. ‌ Also, our teams will work to improve our performance testing capabilities in the development environment to allow more accurate simulation of production load. This will aid us in being able to better detect unoptimized queries before they are released.

Read the full incident report →

Started Aug 26, 2025, 06:29 AM UTC· resolved Aug 26, 2025, 10:21 AM UTC

1. investigating Aug 26, 2025, 06:29 AM UTC

   We are currently investigating an issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

2. identified Aug 26, 2025, 08:02 AM UTC

   We have detected the issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

3. monitoring Aug 26, 2025, 08:14 AM UTC

   We are starting to see recovery post the fix implemented by our service provider for the issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

4. resolved Aug 26, 2025, 10:21 AM UTC

   Duo has confirmed that the issue affecting SMS delivery to phone numbers using T-Mobile services in the US has been fully resolved.

Read the full incident report →

Started Aug 18, 2025, 11:25 AM UTC· resolved Aug 18, 2025, 03:27 PM UTC

1. investigating Aug 18, 2025, 11:25 AM UTC

   We are currently investigating an issue causing phone call authentication failures in India on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

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

   Duo has confirmed that the phone call authentication failures affecting all deployments in India have been fully resolved.

Read the full incident report →

Started Aug 06, 2025, 04:40 AM UTC· resolved Aug 06, 2025, 08:06 AM UTC

1. investigating Aug 06, 2025, 04:40 AM UTC

   We are investigating an issue causing SMS delivery delays and failures in the US. We are waiting for AT&T to fix the issues on their end. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

2. identified Aug 06, 2025, 04:49 AM UTC

   We have identified an issue causing SMS delivery delays and failures in the US. We are waiting for AT&T to fix the issues on their end. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

3. resolved Aug 06, 2025, 08:06 AM UTC

   The issue affecting SMS delivery to US phone numbers has been resolved. Services are now fully operational.

Read the full incident report →

Started Aug 06, 2025, 12:03 AM UTC· resolved Aug 06, 2025, 12:26 AM UTC

1. monitoring Aug 06, 2025, 12:03 AM UTC

   We detected an issue causing login failures when attempting to access the Duo Admin Panel on the DUO41 deployment. We have deployed a fix and monitoring the results at this time.

2. resolved Aug 06, 2025, 12:26 AM UTC

   The issue causing login failures when attempting to access the Duo Admin Panel on the DUO41 deployment has been fully resolved and full functionality is restored.

Read the full incident report →

Started Jul 28, 2025, 12:00 PM UTC· resolved Jul 28, 2025, 01:51 PM UTC

1. investigating Jul 28, 2025, 12:00 PM UTC

   We are currently investigating an issue causing phone call authentication failures in India on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

2. monitoring Jul 28, 2025, 01:25 PM UTC

   The issue causing VoIP authentication failures in India appears to be resolved. We are continuing to monitor the situation closely and will post any updates when the incident is considered fully resolved.

3. resolved Jul 28, 2025, 01:51 PM UTC

   The issue causing VoIP authentication failures in India is now fully resolved.

Read the full incident report →

Started Jul 24, 2025, 01:44 PM UTC· resolved Jul 25, 2025, 12:43 AM UTC

1. investigating Jul 24, 2025, 01:44 PM UTC

   We are currently investigating an issue caused by our UK telephony providers regarding VoIP failures with Duo on DUO70 and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

2. investigating Jul 24, 2025, 01:55 PM UTC

   We are currently investigating an issue caused by our UK telephony providers regarding VoIP failures with Duo on DUO70 and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

3. identified Jul 24, 2025, 02:25 PM UTC

   We have identified the cause of the VoIP authentication failures in Great Britain and our telephony providers in the region are actively working to restore service. While we are monitoring this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations.

4. monitoring Jul 24, 2025, 03:04 PM UTC

   We are actively monitoring the VoIP phone call authentication issue affecting Great Britain.

5. identified Jul 24, 2025, 05:27 PM UTC

   We're continuing to partner with our telephony providers in the region as they work to restore service. Please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations until the issue has been resolved.

6. monitoring Jul 24, 2025, 11:02 PM UTC

   The issue causing VoIP authentication failures in Great Britain appear to be resolved. We are continuing to monitor the situation closely and will post any updates when the incident is considered fully resolved.

7. resolved Jul 25, 2025, 12:43 AM UTC

   The issue causing VoIP authentication failures in Great Britain is now resolved.

Read the full incident report →

Started Jul 23, 2025, 10:33 PM UTC· resolved Jul 24, 2025, 12:33 PM UTC

1. investigating Jul 23, 2025, 10:33 PM UTC

   We are currently investigating an issue with intermittent failures of queries to the Duo AI Assistant for help desk and user manager roles in USA deployments. Direct viewing of authentication logs is not affected.

2. identified Jul 23, 2025, 10:58 PM UTC

   We have identified the issue causing Intermittent failures with Duo AI Assistant.

3. monitoring Jul 24, 2025, 12:26 AM UTC

   We have implemented a fix and we are monitoring the results.

4. resolved Jul 24, 2025, 12:33 PM UTC

   We can confirm that the issue with the Duo AI assistant has been resolved.

Read the full incident report →

Started Jul 17, 2025, 08:42 PM UTC· resolved Jul 17, 2025, 09:04 PM UTC

1. identified Jul 17, 2025, 08:42 PM UTC

   We are currently investigating issues loading SSO pages in the Duo Admin Panel on some deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

2. monitoring Jul 17, 2025, 08:56 PM UTC

   The loading issues affecting Admin Panel SSO Pages are subsiding as our deployment rollout completes. We are continuing to monitor the situation to ensure full resolution.

3. resolved Jul 17, 2025, 09:04 PM UTC

   The issues loading SSO pages in the Admin Panel have been resolved.

Read the full incident report →

Started Jul 17, 2025, 03:44 PM UTC· resolved Jul 17, 2025, 07:05 PM UTC

1. investigating Jul 17, 2025, 03:44 PM UTC

   We are currently investigating reports that our phone numbers are routing to the incorrect endpoints and are working with our internal teams to resolve the issue as soon as possible. If you need to submit a case, please utilize the Duo Support Portal or send us an email to [email protected].

2. identified Jul 17, 2025, 04:53 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 17, 2025, 05:07 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jul 17, 2025, 07:05 PM UTC

   This incident has been resolved.

Read the full incident report →