Duo Security Outage History

Started Sep 03, 2026, 10:04 PM UTC· resolved Sep 03, 2026, 11:24 PM UTC

1. investigating Sep 03, 2026, 10:04 PM UTC

   We are investigating a partial outage affecting Duo hardware token authentication for customers on affected US deployments. Customers using hardware tokens may experience intermittent authentication failures. Based on current information, retrying the authentication attempt is expected to succeed. Other Duo authentication methods are not expected to be impacted and can be used as alternate methods if configured and available. Our engineering team is actively investigating and has started mitigation steps. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

2. monitoring Sep 03, 2026, 10:30 PM UTC

   We have seen the failure rate for Duo hardware token authentication subside on affected US deployments. Customers using hardware tokens may still experience intermittent authentication failures while we continue to monitor. Retrying the authentication attempt is expected to succeed. Other Duo authentication methods are not expected to be impacted and can be used as alternate methods if configured and available. We will continue to monitor service stability and provide additional updates as needed.

3. resolved Sep 03, 2026, 11:24 PM UTC

   This issue has been resolved. Duo hardware token authentication is now functioning normally on affected US deployments. Other Duo authentication methods were not expected to be impacted. Thank you for your patience. If you continue to experience issues, please contact Duo Support.

Read the full incident report →

Started Aug 10, 2026, 08:34 PM UTC· resolved Aug 10, 2026, 10:46 PM UTC

1. investigating Aug 10, 2026, 08:34 PM UTC

   We are investigating an issue affecting the signup service. New account registrations are temporarily unavailable. Our team is actively investigating and working to restore normal service. We apologize for any inconvenience and appreciate your patience.

2. identified Aug 10, 2026, 09:04 PM UTC

   We have identified the issue affecting new account registrations. Our team is working on a fix and expects to release it soon. We apologize for any inconvenience and appreciate your continued patience.

3. resolved Aug 10, 2026, 10:46 PM UTC

   This incident has been resolved. New Duo account registrations are now functioning normally. Thank you for your patience. If you continue to experience issues, please contact Duo Support.

Read the full incident report →

Started Aug 08, 2026, 09:13 PM UTC· resolved Aug 09, 2026, 12:07 AM UTC

1. identified Aug 08, 2026, 09:13 PM UTC

   We have identified an issue causing phone call authentication failures for customers in the United States. This is related to a third-party carrier disruption. We are actively monitoring the carrier issue and working with our provider as needed. Please check back here or subscribe to updates for any changes.

2. monitoring Aug 08, 2026, 11:04 PM UTC

   We are seeing recovery for the issue related to a third-party carrier disruption that caused phone call authentication failures for customers in the United States. We are actively monitoring phone call authentication delivery and will provide another update once the issue is fully resolved.

3. resolved Aug 09, 2026, 12:07 AM UTC

   Phone call authentication delivery for customers in the United States has returned to normal operation. If customers continue to experience issues, please contact Duo Support.

Read the full incident report →

Started Jul 23, 2026, 06:02 PM UTC· resolved Jul 27, 2026, 08:41 PM UTC

1. investigating Jul 23, 2026, 06:02 PM UTC

   We are investigating an issue affecting VoIP and SMS message delivery for users in Israel. The issue is related to an upstream carrier. Our team is working with our providers to investigate and restore normal service. Where available, users can use alternative authentication methods such as Duo Push. We will provide updates as more information becomes available.

2. monitoring Jul 23, 2026, 06:39 PM UTC

   We have implemented a change to address the SMS and VoIP delivery issue affecting users in Israel. SMS and VoIP delivery have recovered, and we are monitoring to confirm continued stability.

3. monitoring Jul 24, 2026, 03:53 PM UTC

   Error rates for SMS and VoIP delivery in Israel have reduced following the implemented change. We are continuing to monitor service behavior and investigate reports of intermittent failures affecting some customers. We will provide another update as more information becomes available.

4. resolved Jul 27, 2026, 08:41 PM UTC

   The SMS and VoIP delivery issue affecting users in Israel has been resolved. If customers continue to experience issues, please contact Duo Support.

Read the full incident report →

Started Jul 07, 2026, 11:15 PM UTC· resolved Jul 08, 2026, 03:01 PM UTC

1. investigating Jul 07, 2026, 11:15 PM UTC

   We are investigating a third-party carrier issue affecting VoIP and SMS services in the Australia region. Customers in Australia may experience delays or failures when using phone call or SMS authentication. Other Duo authentication methods, such as Push Delivery, are not expected to be impacted and can be used as an alternate method of authentication if available. Our team is monitoring the carrier issue and working with the provider as needed. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

2. monitoring Jul 08, 2026, 01:22 AM UTC

   The third-party carrier has indicated that the issue affecting VoIP and SMS services in the Australia region has been resolved. Customers in Australia should see improved delivery for phone call and SMS authentication. Other Duo authentication methods, such as Push Delivery, remain available as alternate authentication methods if configured. We are continuing to monitor service stability and will provide additional updates when the incident is fully resolved.

3. resolved Jul 08, 2026, 03:01 PM UTC

   The third-party carrier issue affecting VoIP and SMS services in the Australia region has been resolved. Phone call and SMS authentication services are operating normally. We appreciate your patience and understanding while we addressed this issue.

Read the full incident report →

Started Jun 23, 2026, 03:58 AM UTC· resolved Jun 23, 2026, 02:21 PM UTC

1. identified Jun 23, 2026, 03:58 AM UTC

   We are currently investigating an issue with SMS for UAE region. Please check back here or subscribe to updates for any changes.

2. monitoring Jun 23, 2026, 08:29 AM UTC

   We have mitigated the SMS delivery issue affecting the UAE region. We are actively monitoring the situation and will provide a final update once the issue is fully resolved.

3. resolved Jun 23, 2026, 02:21 PM UTC

   The SMS delivery issue affecting the UAE region has been resolved. Our team has verified that SMS services are operating normally and full functionality has been restored. Thank you for your patience while we resolved this issue

Read the full incident report →

Started Jun 10, 2026, 02:17 PM UTC· resolved Jun 10, 2026, 03:35 PM UTC

1. investigating Jun 10, 2026, 02:17 PM UTC

   We are currently investigating an issue affecting AI Assistant functionality in the US-W1 (US West-1) region. Users may experience errors or be unable to access AI Assistant features. Our engineering teams are actively investigating the issue and working to restore normal service as quickly as possible. Please check back here or subscribe to updates for the latest information.

2. resolved Jun 10, 2026, 03:35 PM UTC

   The issue affecting AI Assistant functionality in the US-W1 region has been resolved. Our team has verified that services are operating normally, and monitoring has confirmed system stability. Thank you for your patience while we resolved this issue.

Read the full incident report →

Started May 18, 2026, 06:37 PM UTC· resolved May 18, 2026, 08:30 PM UTC

1. investigating May 18, 2026, 06:37 PM UTC

   We are currently investigating an issue with AI Assistant not functioning on all US 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 May 18, 2026, 07:27 PM UTC

   We have implemented mitigation measures and are observing improved AI Assistant performance. We are continuing to monitor success rates and overall service stability.

3. resolved May 18, 2026, 08:30 PM UTC

   The issue affecting AI Assistant functionality across all US deployments has been resolved, and full functionality has been restored. We will continue to monitor service performance to ensure stability.

Read the full incident report →

Started May 13, 2026, 01:22 PM UTC· resolved May 13, 2026, 04:03 PM UTC

1. investigating May 13, 2026, 01:22 PM UTC

   We are currently investigating an issue causing limited authentication failures on DUO57 and are working to correct the issue as soon as possible.

2. identified May 13, 2026, 02:52 PM UTC

   We have identified the cause of the issue causing authentication failures on DUO57 with the Duo Core Authentication Service and are actively working to restore service.

3. monitoring May 13, 2026, 03:37 PM UTC

   We have implemented a fix for the issue causing authentication failures on DUO57 with the Duo Core Authentication Service. We will continue to monitor system performance and authentication success rates and will provide further updates once the incident is fully resolved.

4. resolved May 13, 2026, 04:03 PM UTC

   The issue causing authentication failures on DUO57 with the Duo Core Authentication Service is now resolved and full functionality has been restored.

Read the full incident report →

Started May 07, 2026, 02:17 PM UTC· resolved May 07, 2026, 10:40 PM UTC

1. investigating May 07, 2026, 02:17 PM UTC

   We are investigating an issue causing failures when administrators located in the EU attempt to access the AI Assistant for the first time. Any administrators who have used the Assistant before should still be able to at this time

2. identified May 07, 2026, 04:30 PM UTC

   We’ve identified a problem impacting first-time access to the AI Assistant for administrators in the EU and are actively working to restore normal access. We’ll continue to share updates as progress is made.

3. resolved May 07, 2026, 10:40 PM UTC

   The issue affecting first-time access to the AI Assistant for administrators in the EU has been fully resolved, and normal functionality has been restored.

Read the full incident report →

Started Apr 30, 2026, 05:54 PM UTC· resolved Apr 30, 2026, 06:07 PM UTC

1. identified Apr 30, 2026, 05:54 PM UTC

   We are currently addressing an issue impacting desktop authenticator enrollments .A subset of customers may experience intermittent delays or failures during desktop authenticator enrollment. Mitigation actions are in progress and are helping to reduce impact. Core authentication, SSO, and delivery services remain fully operational.

2. monitoring Apr 30, 2026, 05:57 PM UTC

   Mitigation actions have been implemented. The service has stabilized and recovery is underway. We will continue to monitor to ensure full resolution.

3. resolved Apr 30, 2026, 06:07 PM UTC

   The issue has been resolved. Services have returned to normal operation, and customers should no longer experience delays or failures. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Apr 28, 2026, 02:22 PM UTC· resolved Apr 28, 2026, 03:26 PM UTC

1. investigating Apr 28, 2026, 02:22 PM UTC

   We are investigating elevated authentication latency affecting customers . Authentication requests are continuing to succeed at this time, but customers may experience slower-than-normal response times and degraded performance during login attempts. Our team is actively working to identify the cause and restore normal performance as quickly as possible.

2. monitoring Apr 28, 2026, 02:56 PM UTC

   We have applied mitigation steps and are seeing improved authentication performance for customers in the deployment. Authentication latency has decreased, and the service is recovering. Our team is continuing to monitor the environment closely to ensure stability while we investigate the underlying cause.

3. resolved Apr 28, 2026, 03:26 PM UTC

   The issue causing elevated authentication latency has been fully resolved. Authentication performance has returned to normal levels, and customers should no longer experience delays during login attempts.

Read the full incident report →

Started Apr 18, 2026, 04:30 AM UTC· resolved Apr 18, 2026, 07:09 AM UTC

1. investigating Apr 18, 2026, 04:30 AM UTC

   We are currently detecting an issue with carriers in the US region for SMS delivery. We are currently working with providers to restore the service. In the meantime, please use other means of authentication such as Duo Push.

2. investigating Apr 18, 2026, 05:39 AM UTC

   We are continuing to investigate the SMS delivery issue impacting all customers in the US region. Push notifications will continue to work as expected. Further updates will be provided as more information becomes available.

3. resolved Apr 18, 2026, 07:09 AM UTC

   The SMS delivery issue impacting customers in the US region has been resolved. SMS passcode authentication is now functioning normally. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Mar 22, 2026, 10:13 PM UTC· resolved Mar 23, 2026, 02:23 AM UTC

1. investigating Mar 22, 2026, 10:13 PM UTC

   We are currently observing a recurrence of the issue causing VOIP authentication failures in all deployments in the US region. We are working to correct the issue as soon as possible. While we work to resolve this, please use alternative authentication methods such as Duo Mobile Push, SMS passcodes etc. A full list of available authentication methods can be found here: https://duo.com/docs/policy#authentication-methods

2. monitoring Mar 23, 2026, 12:01 AM UTC

   We are now observing high rates of success of VoIP authentication. The issue appears to be resolved but we will continue to monitor the situation.

3. resolved Mar 23, 2026, 02:23 AM UTC

   VoIP authentication has returned to normal operation with sustained success rates observed.

Read the full incident report →

Started Mar 02, 2026, 08:30 AM UTC· resolved Mar 03, 2026, 11:46 PM UTC

1. investigating Mar 02, 2026, 08:30 AM UTC

   We are currently investigating a service degradation on our DUO81 deployment and are working to restore services as soon as possible.

2. investigating Mar 02, 2026, 08:31 AM UTC

   We are continuing to investigate this issue.

3. identified Mar 02, 2026, 09:01 AM UTC

   We have isolated the issue to a regional outage and are working with our partners to alleviate the degraded performance.

4. identified Mar 02, 2026, 09:01 AM UTC

   We are continuing to work on a fix for this issue.

5. identified Mar 02, 2026, 02:00 PM UTC

   We are continuing to work on a fix for this issue.

6. identified Mar 02, 2026, 02:44 PM UTC

   Our cloud provider is responding to a power outage at a primary data center that continues to cause elevated error rates and connectivity issues across the region. While early signs of recovery were observed, the provider has since confirmed the impact is ongoing. Full restoration and environment stability are expected to take several hours. We will provide our next update within 6 hours.

7. identified Mar 02, 2026, 08:27 PM UTC

   We remain in active coordination with our cloud service provider as they work to resolve a power outage affecting a primary data center. Connectivity issues and elevated error rates across the region will persist until power has been fully restored. The provider has indicated that full restoration and environment stabilization may take a day or more.

8. identified Mar 03, 2026, 07:18 PM UTC

   As previously communicated, a major power and connectivity outage at a third-party data center in the UAE operated by a third-party vendor has impacted Cisco Duo functionality in the region. Our engineering teams have worked continuously to implement local mitigations, but the persistent instability of the regional infrastructure has required more comprehensive measures to ensure business continuity. To fully resolve these issues and restore service stability, Cisco Duo has officially initiated its Disaster Recovery (DR) process. This involves transitioning critical service dependencies and user data away from the affected UAE region to secure, high-availability data centers.

9. resolved Mar 03, 2026, 11:46 PM UTC

   The service outage affecting DUO81 has been resolved. All impacted customers have been successfully migrated to an alternative Duo deployment. This migration has restored full service functionality for all affected users.

Read the full incident report →

Started Mar 01, 2026, 01:29 PM UTC· resolved Mar 01, 2026, 04:39 PM UTC

1. investigating Mar 01, 2026, 01:29 PM UTC

   We are currently investigating a service degradation on our DUO81 deployment and are working to restore services as soon as possible.

2. identified Mar 01, 2026, 02:13 PM UTC

   We have isolated the issue to a regional outage and are rerouting our traffic to alleviate the degraded performance.

3. identified Mar 01, 2026, 03:33 PM UTC

   We are continuing to work to reroute traffic in order to alleviate the degraded performance.

4. monitoring Mar 01, 2026, 04:09 PM UTC

   We have rerouted traffic and are monitoring the behavior for stable, positive results.

5. resolved Mar 01, 2026, 04:39 PM UTC

   The issue was resolved by rerouting traffic.

Read the full incident report →

Started Feb 23, 2026, 03:04 PM UTC· resolved Feb 23, 2026, 05:52 PM UTC

1. investigating Feb 23, 2026, 03:04 PM UTC

   We are currently investigating an issue where 504 Gateway timeouts are present when accessing Entra when Duo is called for MFA. We are working to resolve as quickly as possible.

2. investigating Feb 23, 2026, 04:20 PM UTC

   We are continuing to investigate an issue where 504 Gateway timeouts are present when accessing Entra when Duo is called for MFA. We are working with our respective partners to resolve as quickly as possible.

3. monitoring Feb 23, 2026, 04:38 PM UTC

   We have deployed a fix for the gateway timeouts and are now seeing successful authentications. We are currently monitoring for any further issues.

4. resolved Feb 23, 2026, 05:52 PM UTC

   The issue causing 504 gateway timeouts during Microsoft Entra logins when Duo MFA was called has been fully resolved. Authentication services are operating normally at this time. We will share a root cause analysis once it becomes available.

5. postmortem Feb 25, 2026, 03:01 PM UTC

   # Summary On February 23, 2026, US-based users utilizing the Duo integration with Azure Identity management experienced increased authentication failures and timeouts. These errors were occurring specifically when accessing applications using Microsoft Entra and Duo as the MFA provider. Duo engineering was alerted to the issues via monitoring at 9:15 AM and promptly began investigating various factors that could have caused this error to occur, including checking the health of the different third-party services involved. Finally, the root cause was identified to be increased CPU usage resulting from a code change that added additional validation for security operations. The incident was remediated by scaling the backend services that support this integration. During the incident, updates were posted to the status page as new information became available. At the beginning of the incident, the impact of the issue was underestimated, and thus notifications were not set to go out along with these status updates. When the impact assessment changed, notifications should have been set to go out, but this was missed. Processes have been improved to help prevent this from happening in the future. # Timeline of Events | **Time \(in EST\) 2/23/2026** | **Event** | | --- | --- | | 9:15 am | Engineering begins investigating AzureAuth errors | | 9:27 am | Duo begins receiving reports of 504 gateway timeout errors for customers accessing applications using Microsoft Entra and Duo. | | 10:02 am | First status page from Duo is put up regarding investigating the root cause. This status page is posted without notifications due to assumed scale of incident. | | 11:10 am | Duo scales resources for the Azureauth US deployment. | | 11:19 am | Errors begin to subside. | | 11:24 am | The incident is moved to monitoring. | | 11:30 am | The incident is resolved. | # Root Cause\(s\) The Duo team follows a regular and disciplined release process across all services. Changes are routinely deployed to improve functionality, security posture, and overall reliability. All releases undergo comprehensive validation, including: * Unit testing * Integration testing * Frontend testing * Performance testing This layered testing strategy is designed to identify functional defects, regressions, and performance impacts prior to production deployment. In the days leading up to the incident, a software update was deployed to the backend service that supports the Duo integration with Azure Identity management. This update was part of a broader security improvement effort. The change successfully passed all standard validation processes and was not expected to introduce downtime or performance degradation. During the Monday morning traffic peak, this backend service experienced elevated CPU utilization, resulting in service degradation. The following points all contributed to the service interruption: * **Increased CPU Utilization Per Request** * The deployed change approximately doubled CPU consumption per request within this service. * This materially increased overall compute demand during peak traffic. * **Performance Test Coverage Gaps** * Existing performance tests did not identify the increased CPU usage introduced by the change. * The specific workload characteristics that amplified CPU consumption under peak conditions were not fully represented in pre-production testing. * **Monitoring Gaps** * A recent migration of our monitoring services missed CPU monitors for this service, leading to an alerting gap when CPU consumption started trending upward. * Alerts were triggered only after peak load conditions were reached. # Remediation and Future Work To address all the causes for the incident, Duo is committed to doing the following: * **Addressing increased CPU Utilization per Request** * **This backend service has been scaled up \(Completed\)** * Additional resources have been added to the infrastructure powering this backend service to provide additional compute headroom. * This ensures sufficient capacity to absorb higher per-request of CPU costs. * **Connection Efficiency Improvements \(In Progress\)** * Investigate using persistent connection pooling, and/or caching mechanism to reduce connection overhead and lower per-request for CPU consumption. * **Graceful Degradation Enhancements \(In Progress\)** * Improvements being explored to ensure systems degrade gracefully under high CPU load, with the goal of protecting critical authentication flows and reducing user impact during resource saturation events. * **Addressing Performance Testing Coverage Gaps** * **Expanded Performance Test Coverage \(In Progress\)** * Performance testing will be updated to explicitly model this failure scenario. * Peak-load and stress conditions will be more accurately simulated. * **Performance-Based Release Gates \(In Progress\)** * Performance tests will become release-gating criteria. * Changes that materially impact resource consumption will be identified before production deployment. * **Addressing Monitoring Gaps** * **Capacity Monitoring Enhancement \(Completed\)** * Missing capacity monitors \(inadvertently omitted during a recent migration\) have been restored. * Monitoring coverage for this service has been expanded. * **Comprehensive Monitoring Audit \(Completed\)** * Full audit of all capacity monitors underway to ensure complete monitoring coverage and eliminate similar gaps across services. * **Customer Communication Improvements** * **Improved Status Page Notifications** * Status page processes have been updated to ensure faster and clearer communication. * Commitment to timely, transparent, and regular updates to all customers during future incidents, with notifications.

Read the full incident report →

Started Feb 23, 2026, 02:02 PM UTC· resolved Feb 23, 2026, 06:20 PM UTC

1. investigating Feb 23, 2026, 02:02 PM UTC

   We are currently investigating an issue causing an abnormal phone call authentication success rate for the US region. Please check back here or subscribe to updates for any changes.

2. monitoring Feb 23, 2026, 05:26 PM UTC

   The issue causing an abnormal phone call authentication success rate is tied to a third-party carrier. We are monitoring the third-party's communications at this time and can confirm that Duo telephony services are functioning as expected at this time.

3. resolved Feb 23, 2026, 06:20 PM UTC

   The issue causing an abnormal phone call authentication success rate has been resolved by the third-party carrier.

Read the full incident report →

Started Feb 19, 2026, 02:46 PM UTC· resolved Feb 19, 2026, 06:01 PM UTC

1. investigating Feb 19, 2026, 02:46 PM UTC

   We are investigating an issue causing the AI Assistant to be unavailable for administrators in India. Please check back here or subscribe to updates for any changes.

2. monitoring Feb 19, 2026, 05:47 PM UTC

   We have deployed a fix for the issue causing the AI Assistant to be unavailable for administrators in India and are monitoring the results of the fix at this time.

3. resolved Feb 19, 2026, 06:01 PM UTC

   The issue causing the AI Assistant to be unavailable for administrators in India has been resolved.

Read the full incident report →

Started Feb 19, 2026, 02:35 PM UTC· resolved Feb 19, 2026, 10:32 PM UTC

1. investigating Feb 19, 2026, 02:35 PM UTC

   We are investigating an issue causing failures when administrators attempt to access the AI Assistant for the first time. Any administrators who have used the Assistant before should still be able to at this time. Please check back here or subscribe to updates for any changes.

2. identified Feb 19, 2026, 05:47 PM UTC

   We have identified the issue causing failures when administrators attempt to access the AI Assistant for the first time and are working to deploy a fix at this time.

3. monitoring Feb 19, 2026, 09:30 PM UTC

   We are currently monitoring the results of a deployed fix for the issue causing failures when administrators attempt to access the AI assistance for the first time.

4. resolved Feb 19, 2026, 10:32 PM UTC

   The deployed fix for this incident has resolved the issue. We will continue to monitor these results.

Read the full incident report →

Started Feb 04, 2026, 06:55 PM UTC· resolved Feb 05, 2026, 01:11 AM UTC

1. identified Feb 04, 2026, 06:55 PM UTC

   We have Identified the cause of enrollment failures that display the error message "Your session has expired. Please try again." and are working to correct the issue as soon as possible. As a workaround: -If using enrollment email links, update the enrollment experience settings (https://duo.com/docs/administration-settings#enrollment) to show New Universal Prompt. -If enrolling using in-line self enrollment with an existing application (https://duo.com/docs/enrolling-users#inline-self-enrollment), update that application to use the Universal Prompt (https://duo.com/docs/universal-prompt-update-guide). -You can also enroll users manually from the Duo Admin Panel (https://duo.com/docs/administration-devices#adding-a-2fa-device-to-a-user) or issue an enrollment code for self-enrollment (https://duo.com/docs/enrolling-users#generate-enrollment-codes-for-existing-users). Please check back here or subscribe to updates for any changes.

2. monitoring Feb 05, 2026, 12:56 AM UTC

   We have implemented a fix for the enrollment failures that caused the error message "Your session has expired. Please try again." and are monitoring the results closely.

3. resolved Feb 05, 2026, 01:11 AM UTC

   The issue causing enrollment failures that display the error message "Your session has expired. Please try again." has been resolved.

4. postmortem Feb 10, 2026, 09:18 PM UTC

   # **Enrollment Timeout Outage** Incident Report – 02/04/2026 ## Summary A recent software update Duo made related to certificate security improvements inadvertently changed the order of operations for user sessions in our legacy enrollment experience. This resulted in user sessions not being properly initialized, prompting the system to mistakenly identify these sessions as expired. Affected users were unable to complete enrollment and saw the message: “Your session has expired. Please try again.” The issue only affected enrollment flows using the legacy Traditional Prompt. Customers were able to successfully enroll by switching to the Universal Prompt enrollment experience as a workaround. Duo identified and corrected the issue by ensuring sessions are fully initialized before they are used. The fix was deployed on 2026-02-04, and enrollment is now functioning normally. Duo has implemented additional safeguards to prevent similar session handling issues in future updates. ## Timeline of Events **Date/Time \(in EST\)** 02/04/2026 03:57AM - Duo receives reports that customers are unable to complete enrollments 02/04/2026 09:00 AM - Authentication team starts investigating 02/04/2026 10:42 AM - Authentication team identifies root cause 02/04/2026 3:40 PM - The fix begins rolling out to customers 02/04/2026 7:26 PM - The fix finishes rolling out to customers 02/04/2026 7:26 PM - Duo confirms that enrollments are working as intended

Read the full incident report →

Started Jan 22, 2026, 06:36 PM UTC· resolved Jan 22, 2026, 08:18 PM UTC

1. investigating Jan 22, 2026, 06:36 PM UTC

   We are investigating an issue causing authentication failures on our DUO4 deployment. Please check back here or subscribe to updates for any changes.

2. resolved Jan 22, 2026, 08:18 PM UTC

   The issue causing authentication failures on our DUO4 deployment has been resolved.

Read the full incident report →

Started Jan 21, 2026, 09:38 PM UTC· resolved Jan 21, 2026, 11:32 PM UTC

1. investigating Jan 21, 2026, 09:38 PM UTC

   We are currently investigating an issue causing authentication failures with the authentications for newly created MSP sub-accounts 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 Jan 21, 2026, 09:57 PM UTC

   We have identified the cause of authentication failures for newly created MSP sub-accounts and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

3. resolved Jan 21, 2026, 11:32 PM UTC

   We have identified the cause of the issue for authentication failures with newly created MSP Sub-accounts on all our deployments and remediation steps have been applied to correct this. If you continue to experience any additional issues related to this, please contact us at https://duo.com/support referencing this incident, (https://status.duo.com/incidents/tymgyq32v7dw).

Read the full incident report →

Started Jan 14, 2026, 07:35 PM UTC· resolved Jan 15, 2026, 06:16 AM UTC

1. investigating Jan 14, 2026, 07:35 PM UTC

   There has been an uptick in authentication failures using SMS, Phone Call, and Push as there are ongoing phone carrier outages. Please attempt to leverage our other approved MFA methods, such as Duo Mobile Passcodes, Hardware Tokens, and Security Keys, or move your mobile device to a WiFi connection so that Pushes can be properly received. Please check back here or subscribe to updates for any changes.

2. identified Jan 14, 2026, 08:01 PM UTC

   We have confirmed that the authentication failures using SMS, Phone Call, and Push are due to ongoing cellular carrier outages. Please attempt to leverage our other approved MFA methods, such as Duo Mobile Passcodes, Hardware Tokens, and Security Keys, or move your mobile device to a WiFi connection so that Pushes can be properly received.

3. monitoring Jan 15, 2026, 04:30 AM UTC

   We are starting to see recovery post the fix implemented by our service provider for the issue affecting SMS, Phone Call, and Push delivery. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

4. resolved Jan 15, 2026, 06:16 AM UTC

   According to our telephony service provider, the issue affecting SMS, Phone Call, and Push delivery has been resolved. Currently our services are now back to normal.

Read the full incident report →

Started Dec 23, 2025, 07:35 AM UTC· resolved Dec 23, 2025, 08:59 AM UTC

1. investigating Dec 23, 2025, 07:35 AM UTC

   Duo Support is currently investigating an issue disrupting call connectivity between customers and our Support Engineers. We are working with the appropriate teams to address the core issue. If you need to contact Duo Support, we recommend contacting us via alternative channels of Email ([email protected]) and Support Portal.

2. identified Dec 23, 2025, 07:56 AM UTC

   Duo Support has identified the issue disrupting call connectivity between customers and our Support Engineers and is actively working with the appropriate teams to address the core issue. If you need to contact Duo Support, we recommend using alternative channels such as email ([email protected]) or the Support Portal. We apologize for the inconvenience and appreciate your patience as we work to resolve this issue.

3. monitoring Dec 23, 2025, 08:33 AM UTC

   A fix has been implemented to resolve the call connectivity issue between customers and our Support Engineers. We are currently monitoring the situation with the appropriate teams to ensure continued service stability.

4. resolved Dec 23, 2025, 08:59 AM UTC

   The issue affecting call connectivity between customers and our Support Engineers has been resolved.

Read the full incident report →