Duo Security

Affected: Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 22:04 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...

2. monitoring 2026-09-03 22:30 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...

3. resolved 2026-09-03 23:24 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-10 20:34 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 2026-08-10 21:04 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 2026-08-10 22:46 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-08 21:13 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...

2. monitoring 2026-08-08 23:04 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...

3. resolved 2026-08-09 00:07 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 18:02 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...

2. monitoring 2026-07-23 18:39 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 2026-07-24 15:53 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...

4. resolved 2026-07-27 20:41 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-07 23:15 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...

2. monitoring 2026-07-08 01:22 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,...

3. resolved 2026-07-08 15:01 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-23 03:58 UTC

   We have identified the issue related to SMS for UAE region and are working to resolve it. Users have the option to use alternative auth methods, like Duo Push or VoIP. Please check back here or subscribe to updates for any changes.

2. monitoring 2026-06-23 08:29 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 2026-06-23 14:21 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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-10 14:17 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...

2. resolved 2026-06-10 15:35 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-18 18:37 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 2026-05-18 19:27 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 2026-05-18 20:30 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 13:22 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 2026-05-13 14:52 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 2026-05-13 15:37 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 2026-05-13 16:03 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-07 14:17 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 2026-05-07 16:30 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 2026-05-07 22:40 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-30 17:54 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...

2. monitoring 2026-04-30 17:57 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 2026-04-30 18:07 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 14:22 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...

2. monitoring 2026-04-28 14:56 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...

3. resolved 2026-04-28 15:26 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-18 04:30 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 2026-04-18 05:39 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 2026-04-18 07:09 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-22 22:13 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...

2. monitoring 2026-03-23 00:01 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 2026-03-23 02:23 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-22 17:18 UTC

   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. A...

2. investigating 2026-03-22 19:13 UTC

   We are observing a recovery in voice call processing across the U.S. and are continuing to investigate the root cause of this impact.

3. monitoring 2026-03-22 20:00 UTC

   We are now observing high rates of success of VoIP authentication. We will continue to monitor the situation.

4. resolved 2026-03-22 20:33 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Admin Panel, Push Delivery, Phone Call Delivery, SMS Message Delivery, Cloud PKI, SSO

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-02 08:30 UTC

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

2. investigating 2026-03-02 08:31 UTC

   We are continuing to investigate this issue.

3. identified 2026-03-02 09:01 UTC

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

4. identified 2026-03-02 09:01 UTC

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

5. identified 2026-03-02 14:00 UTC

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

6. identified 2026-03-02 14:44 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...

7. identified 2026-03-02 20:27 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...

8. identified 2026-03-03 19:18 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...

9. resolved 2026-03-03 23:46 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Admin Panel, Push Delivery, Phone Call Delivery, SMS Message Delivery, Cloud PKI, SSO

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-01 13:29 UTC

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

2. identified 2026-03-01 14:13 UTC

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

3. identified 2026-03-01 15:33 UTC

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

4. monitoring 2026-03-01 16:09 UTC

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

5. resolved 2026-03-01 16:39 UTC

   The issue was resolved by rerouting traffic.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-02-23 15:04 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 2026-02-23 16:20 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 2026-02-23 16:38 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 2026-02-23 17:52 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 2026-02-25 15:01 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-23 14:02 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 2026-02-23 17:26 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 2026-02-23 18:20 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-19 14:46 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 2026-02-19 17:47 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 2026-02-19 18:01 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-19 14:35 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 2026-02-19 17:47 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 2026-02-19 21:30 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 2026-02-19 22:32 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-18 18:28 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.

2. identified 2026-02-18 19:48 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. resolved 2026-02-19 01:31 UTC

   The issue causing the failures for administrators access of the AI Assistant 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-04 18:55 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...

2. monitoring 2026-02-05 00:56 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 2026-02-05 01:11 UTC

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

4. postmortem 2026-02-10 21:18 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 18:36 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 2026-01-22 20:18 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-21 21:38 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 2026-01-21 21:57 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 2026-01-21 23:32 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-14 19:35 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...

2. identified 2026-01-14 20:01 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...

3. monitoring 2026-01-15 04:30 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 2026-01-15 06:16 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Support

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-23 07:35 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...

2. identified 2025-12-23 07:56 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...

3. monitoring 2025-12-23 08:33 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 2025-12-23 08:59 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-19 17:59 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 2025-12-19 19:12 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 2025-12-19 20:24 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 2025-12-19 21:03 UTC

   The issue affecting Duo Trial signups has been resolved.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, Phone Call Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 08:29 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 2025-10-20 08:52 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...

3. resolved 2025-10-20 11:06 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-20 07:54 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...

2. identified 2025-10-20 09:44 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 2025-10-20 11:20 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Admin Panel, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-15 12:19 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...

2. identified 2025-10-15 16:00 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:...

3. resolved 2025-10-15 20:01 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Admin Panel, Push Delivery, Phone Call Delivery, SMS Message Delivery

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-07 19:13 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 2025-10-07 19:23 UTC

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

3. monitoring 2025-10-07 19:44 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 2025-10-07 19:56 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 2025-10-09 14:04 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-29 09:46 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 2025-09-29 10:32 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...

3. identified 2025-09-29 16:16 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 support@duo.com or give us a call at the number...

4. resolved 2025-09-29 16:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-26 14:54 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 2025-09-26 21:42 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 2025-09-26 22:41 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-09 16:44 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 2025-09-09 16:54 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 2025-09-09 17:09 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 2025-09-10 21:27 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Admin Panel, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service, Core Authentication Service

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-08-29 17:30 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...

2. monitoring 2025-08-30 04:05 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 2025-08-30 05:03 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 2025-09-03 15:10 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, SSO, SSO, SSO, SSO, SSO, SSO

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-26 14:43 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 2025-08-26 14:48 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 2025-08-26 14:58 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, SSO, SSO, SSO

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-26 08:08 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 2025-08-26 08:09 UTC

   We are continuing to investigate this issue.

3. identified 2025-08-26 09:06 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 2025-08-26 09:29 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 2025-08-26 11:43 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...

6. postmortem 2025-08-29 18:50 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...

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-26 06:29 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 2025-08-26 08:02 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 2025-08-26 08:14 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...

4. resolved 2025-08-26 10:21 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, SMS Message Delivery

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-18 11:25 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 2025-08-18 15:27 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery, SMS Message Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-06 04:40 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...

2. identified 2025-08-06 04:49 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...

3. resolved 2025-08-06 08:06 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-08-06 00:03 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 2025-08-06 00:26 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.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-01 00:16 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. identified 2025-08-01 00:45 UTC

   We have identified the cause of the AI Assistant issue for all US deployments and are actively working to restore the service.

3. monitoring 2025-08-01 01:39 UTC

   We have implemented a fix for the issue with AI Assistant in all US deployments. We will continue to monitor the issue and will post any updates when the incident is considered fully resolved.

4. resolved 2025-08-01 03:27 UTC

   The issue with AI Assistant failures in all US deployments is now resolved and full functionality is restored.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-31 12:04 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. identified 2025-07-31 18:27 UTC

   We have identified the cause of the VoIP authentication failures in India and are working on a solution. In the meantime, a workaround has been applied and we are seeing increased success rates. Please check back here or subscribe to updates for any changes.

3. monitoring 2025-07-31 21:49 UTC

   We are now observing high rates of success of VoIP authentication in India. We will continue to monitor the authentications and post any updates if the situation changes or if the incident is considered fully resolved.

4. resolved 2025-07-31 23:50 UTC

   The issue causing VoIP authentication failures in India is resolved and VoIP authentication services are functioning as expected.

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-30 09:30 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 2025-07-30 10:24 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 2025-07-30 11:14 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-28 12:00 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 2025-07-28 13:25 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 2025-07-28 13:51 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery, Phone Call Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-24 13:44 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 2025-07-24 13:55 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 2025-07-24 14:25 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,...

4. monitoring 2025-07-24 15:04 UTC

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

5. identified 2025-07-24 17:27 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...

6. monitoring 2025-07-24 23:02 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 2025-07-25 00:43 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant, AI Assistant

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-23 22:33 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 2025-07-23 22:58 UTC

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

3. monitoring 2025-07-24 00:26 UTC

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

4. resolved 2025-07-24 12:33 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel, Admin Panel

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-07-17 20:42 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 2025-07-17 20:56 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 2025-07-17 21:04 UTC

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

Excerpts are shortened. Read the full incident on Duo Security's status page.

Affected: Phone Support

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-17 15:44 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...

2. identified 2025-07-17 16:53 UTC

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

3. monitoring 2025-07-17 17:07 UTC

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

4. resolved 2025-07-17 19:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Duo Security's status page.