Duo Security outage history

Users on US deployments experienced intermittent failures when signing in with Duo hardware tokens, while other authentication methods remained available if configured. The issue began around 10:06 PM UTC and affected a broad set of Core Authentication Services, including DUO17, DUO22, DUO39, DUO40, DUO42, DUO49, DUO50, DUO52, DUO55, DUO56, DUO58, DUO61, DUO62, DUO63, DUO65, DUO72, DUO73, DUO74, DUO75, DUO76, DUO77, DUO78, and DUO9. Duo noted that hardware token authentication could fail intermittently and advised users to retry, with other methods remaining available if configured.

New account registrations were temporarily unavailable as Duo Security's signup service encountered an outage. The issue began at 8:35 PM UTC and affected new signups for about two hours, with users unable to create accounts during that window. Duo Security provided status updates indicating ongoing investigation and efforts to restore the signup service.

Updates from Duo Security confirmed the issue was identified and a fix was being prepared, with the signup service restored by 10:50 PM UTC. Users could once again sign up after the outage, though some onboarding steps may have been paused during the incident.

Duo Security reported an incident affecting US customers where phone-based authentication calls failed due to a disruption with a third-party carrier. Access to second-factor verification via Duo's phone delivery could be disrupted, as many Phone Call Delivery components were affected. The issue began at Aug 8, 2026 9:15 PM UTC and was largely resolved by 12:11 AM UTC, as the carrier disruption subsided and services recovered across the impacted delivery paths.

Duo Security actively monitored the situation and coordinated with the carrier, posting updates as recovery progressed. By the early hours, the majority of affected components returned to normal operation, restoring phone-based authentication for most users.

An interruption affected VoIP and SMS delivery used for Duo authentication for users in Israel. The disruption prevented delivery of verification codes and authentication calls, attributed to an upstream carrier issue. Duo Security investigated with the carrier and recommended using alternative methods such as Duo Push while service was restored. The issue began at 6:05 PM UTC and was resolved by 6:40 PM UTC.

In Australia, Duo Security users experienced delays and failures when using phone call or SMS authentication because a third-party carrier issue affected VoIP and SMS services in the region. Other authentication methods, such as Push Delivery, remained available where configured. The impacted delivery methods were DUO66 / Phone Call Delivery and DUO66 / SMS Message Delivery. The disruption lasted for much of the period, with intermittent improvements as status updates were issued.

The Duo Security outage affected US deployments during sign-ins using Microsoft Entra MFA, with users seeing 504 gateway timeouts when authenticating. The issue began around 2:06 PM UTC and quickly manifested as widespread login failures across the United States, with a notable surge in user reports around 3:00 PM UTC indicating broad impact across multiple regions. The disruption impacted core authentication functionality and related Phone Call Delivery components, hindering access to apps that rely on Duo for multi-factor authentication.

Duo's status updates identified Entra MFA gateway timeouts and associated delivery issues, with a fix deployed around 4:40 PM UTC and ongoing monitoring thereafter. The outage lasted roughly 3:05 PM UTC to 4:40 PM UTC (about 1 hour 35 minutes) before services began to stabilize. By around 6:20 PM UTC many core authentication and Phone Call Delivery components were reported as operational again, with continued checks to ensure full restoration across all affected deployments.

Users attempting to authenticate with Duo Security during the DUO4 deployment faced authentication failures, impacting login flows that rely on Duo for multi-factor authentication and affecting access to services protected by Duo 2FA. The incident began at 6:40 PM UTC and was resolved by 8:20 PM UTC, lasting about 1 hour and 40 minutes. The provider issued 2 official status updates during the incident as teams investigated and then restored normal operation.

Duo Security experienced a disruption in its Support Phone System, causing issues with call connectivity between customers and Duo Support Engineers. This affected the Duo Support / Phone Support channel and temporarily hindered phone-based contacts. Duo advised customers to use alternate channels, such as email (support@duo.com) and the Support Portal, while the issue was investigated. The outage began at 7:40 AM UTC and was resolved by 9:00 AM UTC.

From Oct 20, 2025 7:55 AM UTC, Duo Security experienced email delivery issues across all deployments, affecting email-based communications and related authentication workflows. The disruption expanded by Oct 20, 2025 8:35 AM UTC to include phone call and SMS delivery for authentication, with a large set of Duo Admin Panel components showing degraded behavior. The incident prompted five status updates and led to a broad degradation affecting dozens of Admin Panel components. The outage persisted for most of Oct 20 and into Oct 21, with recovery beginning around Oct 21, 2025 3:00 AM UTC. User reports from Denver and Knoxville described login push delays and related access issues during the event.

Duo Security experienced an authentication outage in which Duo Desktop was not recognized during authentications on Windows 11 25H2, causing sign-in failures for users relying on Duo for MFA. The issue affected multiple core authentication services and the Admin Panel, impacting a broad set of Duo components and preventing successful logins. The outage began at 12:20 PM UTC and was resolved by 8:06 PM UTC, lasting approximately 7 hours and 46 minutes. The incident included two official status updates documenting the investigation and restoration steps, and listed the affected components on the status page. Duo recommended avoiding the Windows 11 25H2 upgrade and, if already upgraded, downgrading to the previous version to resolve the problem.