In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 10, 2026 - 15:00 EST
Scheduled - Beginning February 2nd, customers using outdated Duo-connected applications or clients may experience authentication failures. Impacted customers should update all affected applications and Duo Mobile apps to the latest versions with the new Duo CA pinning bundle. Impact can be confirmed via the Unsupported Clients Log in the Duo Admin Panel, and full guidance is available in Duo documentation and Cisco Field Notice FN74372.
This page provides status information on the services that are part of Duo Security. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact support. You can find your deployment ID in the Duo Admin Panel under Help.
The Duo Guide to Business Continuity will help you understand the two categories of Duo service outages, Duo’s failure modes and how to decide on Fail Safe vs. Fail Secure, how your applications will respond to different types of outages, and be prepared to message your users during an outage.
If you have any questions beyond the updates provided here, please contact us at support@duo.com.
Cisco is committed to providing you with a secure and reliable experience. To ensure our DUO platform continues to meet your needs, we will be performing maintenance.
Maintenance Details : Duo will be performing a staged rollout to rotate its server certificates to a new Root Certificate Authority (CA) bundle. This process will occur globally across all Commercial and Federal deployments.
Date and Time: April 1st, 16:00 UTC to April 10th, 00:00 UTC
Impact: Updated Clients: Customers who have already updated their Duo software to the required versions will experience no service disruption.
Outdated Clients: Effective April 15, 2026, major browsers and operating systems will no longer trust the DigiCert G1 root certificate. Consequently, Duo protected applications and integrations running unsupported versions will experience authentication failures such as Duo Push delivery issues or API errors. As this is a mandatory, device-level change, in order to prevent service disruptions, all systems must be updated to supported versions.
Action Required Please ensure your environment is running the required software versions to prevent service disruption. For a full list of required versions and technical guidance, please refer to our official documentation
Data Centers Region: Global (All Commercial and Federal deployments)
Services: Duo Authentication Proxy Duo Mobile (Android & iOS) Duo API & SDKs Duo Universal Prompt Various Duo-developed and partner integrations (refer to Field Notice FN74372)
We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support Posted on
Mar 31, 2026 - 17:35 EDT
Resolved -
VoIP authentication has returned to normal operation with sustained success rates observed.
Mar 22, 22:23 EDT
Monitoring -
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.
Mar 22, 20:01 EDT
Investigating -
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.
Resolved -
VoIP authentication has returned to normal operation with sustained success rates observed.
Mar 22, 16:33 EDT
Monitoring -
We are now observing high rates of success of VoIP authentication. We will continue to monitor the situation.
Mar 22, 16:00 EDT
Update -
We are observing a recovery in voice call processing across the U.S. and are continuing to investigate the root cause of this impact.
Mar 22, 15:13 EDT
Investigating -
We are currently investigating an issue causing VOIP authentication failures in all the deployments in the US region and are working to correct the issue as soon as possible. At this time please use alternative authentication methods such as Duo Mobile Push, or SMS passcodes.