Duo Security Outage History

Duo Security experienced SMS delivery failures affecting all customers in the US region due to carrier issues, preventing users from receiving SMS passcode authentication messages. The incident lasted 2.7 hours while Duo worked with SMS providers to restore service, with users able to use alternative authentication methods like Duo Push during the outage. SMS passcode authentication was fully restored and functioning normally after the resolution.

Duo Security experienced VOIP phone call authentication failures affecting all US region deployments for 4.2 hours. Users were unable to authenticate via phone calls but could use alternative methods like Duo Mobile Push and SMS passcodes. The issue was resolved with VoIP authentication returning to normal operation and sustained success rates.

Duo Security experienced a 3.3-hour outage affecting VOIP phone call authentication for all US-based deployments, preventing users from completing two-factor authentication via voice calls. Users were advised to use alternative authentication methods including Duo Mobile Push notifications or SMS passcodes during the incident. The service was fully restored with normal VOIP authentication operations resuming after monitoring confirmed sustained success rates.

A power outage at a third-party data center in the UAE caused a 39-hour service outage affecting Duo Security's DUO81 deployment, impacting all core authentication services including SSO, push notifications, SMS delivery, phone calls, and admin panels. Due to persistent infrastructure instability in the region, Cisco Duo activated its disaster recovery process and migrated all affected customers to alternative data centers to restore full functionality.

Duo Security experienced a service degradation on their DUO81 deployment that affected multiple core services including authentication, SMS/phone delivery, push notifications, SSO, admin panel, and Cloud PKI for 3.2 hours. The issue was identified as a regional outage that impacted service performance across these critical authentication components. The incident was resolved by rerouting traffic away from the affected region to restore normal service operation.

Duo Security experienced 504 gateway timeouts when users attempted to access Microsoft Entra (formerly Azure AD) and Duo was called for multi-factor authentication, preventing users from logging into Microsoft products like Outlook and Teams. The Core Authentication Service was affected for 2.9 hours across all deployments. The issue was resolved after deploying a fix, restoring normal authentication functionality.

Duo Security experienced phone call authentication failures in the US region for 4.3 hours, causing an abnormally low success rate for users attempting to authenticate via phone calls. The issue was traced to a third-party carrier problem and was resolved once the carrier fixed their systems.