Is Duo Down Right Now? Check if there is a current outage ongoing.

We are currently investigating an issue causing phone call authentication failures In India on all our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing login failures and "Invalid Credentials" messages when attempting to access the Duo Admin Panel. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

While we have identified the issue causing SMS delivery failures in the Netherlands & Australia. We are waiting for our provider 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 Duo-protected integrations.

We are currently investigating an issue affecting SMS delivery to phone numbers in Netherlands & Australia. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

The issue causing authentication failures on DUO64 for some users has been fully resolved.

We have identified the issue and have a fix rolling out now.

We are investigating authentication failures for some users on the DUO64 deployment, and will share more details as soon as possible.

We are investigating authentication failures for some users on the DUO64 deployment, and will share more details as soon as possible.

The third-party issue with intermittent SMS delivery failures for Greece has been resolved.

We have implemented a workaround for the third-party issue with intermittent SMS delivery failures in Greece and are monitoring the results at this time.

While we have identified the issue causing SMS delivery failures in the Greece. We are waiting for a solution and will provide updates as they are available. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

We are currently investigating an issue affecting SMS delivery to phone numbers in Greece. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

We are currently investigating an issue affecting SMS delivery to phone numbers in Greece.Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

## Summary  On May 19, 2025, around 19:00 ET, Duo received reports of users who were unable to reset their Active Directory \(AD\) passwords through Duo SSO. This impacted all users who were attempting to reset an expired AD password. Functionality was restored to all deployments at 20:46 ET.   ## Timeline of Events  12:53 ET: A planned update to SSO services is rolled out.  19:05 ET: Duo engineering is alerted of multiple customers who are unable to reset expired passwords for AD  19:26 ET: Duo begins deploying a fix for the expired password reset issue  19:57 ET: Duo receives confirmation that some customers are seeing restored service, fix continues to be rolled out for additional deployments  20:46 ET: Fix is rolled out to all deployments and service is restored  ## Details  An update was released that introduced a code change to our logic for determining whether or not to direct users to reset their expired AD password. This code change contained a bug which resulted in authentications being mistaken as invalid instead of requiring a password change.  During the duration of this issue, 526 customers were identified as having one or more users who were blocked from resetting their password.  ### In addition to fixing the bug that caused this issue:  * Engineering is planning to increase our observability on this specific type of issue to improve our response time in the future.  * Engineering is planning to improve our automated testing for this password reset flow.

We can confirm that the issue with the Password reset for Duo SSO logins using Active Directory has been resolved. Please check back here or subscribe for updates on the RCA as soon as it becomes available.

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

We have identified the issue and a fix is being deployed.

We are currently investigating an issue causing password reset failures for Duo SSO logins using Active Directory as an authentication source.

We are currently investigating an issue causing password reset failures for Duo SSO logins using Active Directory as an authentication source.

After continued monitoring, we can confirm that the issue causing intermittent authentication delays for Duo SSO logins using Active Directory, affecting a small subset of customers, has been resolved.

We have identified that the issue causing intermittent authentication delays for Duo SSO logins using Active Directory affected a small subset of customers and has since resolved as it was caused by outside factors. We are continuing to monitor for any further delays at this time.

We are currently investigating an issue causing intermittent authentication delays for Duo SSO logins using Active Directory as an authentication source. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing intermittent authentication delays for Duo SSO logins using Active Directory as an authentication source. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing intermittent authentication delays for Duo SSO logins using Active Directory as an authentication source.Please check back here or subscribe to updates for any changes.

We are no longer seeing outage reports from the backend provider. All services are considered fully operational.

We are seeing improvements in the outage reports of the backend provider and are monitoring phone callback authentication success rates for the area. Please check back here or subscribe to updates for any changes.

We have identified a backend provider issue causing degradation in India VOIP services causing MFA calls to intermittently fail and are waiting on a fix. As a workaround, please continue to leverage one of our other support MFA methods including Push, Hardware Tokens, and Security Keys. Please check back here or subscribe to updates for any changes.

We are continuing to investigate this issue.

We are currently investigating an issue causing degradation in India VOIP services resulting in MFA calls failing intermittently. As a workaround, please leverage one of our other support MFA methods including Push, Hardware Tokens, and Security Keys. Please check back here or subscribe to updates for any changes.

We are continuing to investigate this issue.

We are currently investigating an issue causing degradation in India VOIP services resulting in MFA calls failing intermittently. As a workaround, please leverage one of our other support MFA methods including Push, Hardware Tokens, and Security Keys.Please check back here or subscribe to updates for any changes.

After continued monitoring of the third-party carrier's status, the issue causing intermittent SMS delivery to the US region is resolved.

We have identified the issue causing intermittent SMS delivery failures in the US region to be caused by a third party carrier. We are monitoring the carrier's status at this time.

We are currently investigating an issue causing intermittent SMS delivery failures in the US region. While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing intermittent SMS delivery failures in the US region.While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations.Please check back here or subscribe to updates for any changes.

The third-party issue with intermittent phone call failures for India has been resolved.

We have implemented a workaround for the third-party issue with intermittent phone call failures in India and are monitoring the results at this time.

We are currently investigating an issue causing intermittent phone call failures in India. While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing intermittent phone call failures in India.While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations.Please check back here or subscribe to updates for any changes.

The third-party issue with intermittent phone call failures for the US region has been resolved.

We have implemented a workaround for the third-party issue with intermittent phone call failures in the US region and are monitoring the results at this time.

We are currently investigating an issue causing intermittent phone call failures in the US region. While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations. Please check back here or subscribe to updates for any changes.

We are currently investigating an issue causing intermittent phone call failures in the US region.While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc. to login to your Duo-protected integrations.Please check back here or subscribe to updates for any changes.

## Summary  On February 24, 2025, 9:47 am EST, Duo experienced a service disruption affecting the Admin Panel. The incident impacted customers using the discovery service, which is primarily used by managed service provider \(MSP\) administrators for managing subaccounts in a multi-tenant environment.   The incident was mitigated at 11:15 am. After monitoring the success of the fix, the incident was resolved at 12:00 pm.    ## Details  The disruption resulted from a performance issue with database queries in the discovery service, leading to problems logging into the Admin Panel login and searching or navigating subaccount-related features. The slow running query caused excessive database load during subaccount searches. The query's performance degraded with growing customer subaccount search, leading to slow response times.  Customers without multi-tenancy and/or not using discovery service were not affected, and the outage did not impact any authentication services. The issue was mitigated by scaling up the database instance to provide more headroom and fixing the slow database query.   The issue was identified prior to this outage and the development team had fixes that were planned for the next Duo release version. However, a spike in customer traffic caused this incident before that version was rolled out.    ## What is Duo doing to prevent this in the future?  In the short term, Duo has further optimized the database query to enhance performance and will add additional read replicas to alleviate load on the primary database. In the long term, Duo is implementing a range of performance improvements, including caching on the admin panel, to further reduce database load during subaccount operations.

We have confirmed that the implemented fix has resolved the issue. Admin Panel logins are now fully operational. An RCA will be posted once it has been completed.

A fix has been implemented and we're starting to see recovery. We will continue to monitor the results.

The issue causing problems with Admin Panel logins has been identified and a fix is being worked on.

We are currently investigating an issue causing login issues with the Duo Admin Panel 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.

Summary  From January 17, 2025, to February 5, 2025, a prolonged SMS delivery issue in the United Arab Emirates \(UAE\) region caused complete SMS authentication failures. The failures were caused by the blocking of Duo’s sender identification by regional carriers.    The issue was resolved by renewing the sender identification used by our vendor for the UAE region.  Timeline of Events   January 17, 2025   10:45 UTC: SMS failures are reported, and investigation begins.  10:50 Engineering sends traffic from primary provider to secondary provider. Traffic success does not improve.  11:15: A support request with the primary and secondary SMS vendor is opened. The vendors cite downstream providers as the root cause.  15:00: Issue is escalated further to the vendors. They request Duo re-register their sender identification.  January 19-24, 2025: Ongoing communication and escalation with vendors.  January 24, 2025: Legal documentation process initiated to re-register sender identification.  January 31, 2025: Traffic is redirected to another vendor but is unsuccessful due to downstream carrier issues.  February 5, 2025: SMS services restored after being unblocking by the vendor.  Details  Duo worked diligently to partner with our vendors to restore service as quickly as possible. We have requested a root cause analysis from our vendor and will provide further updates when it is made available.

The issue causing intermittent SMS delivery failures in the UAE has been resolved.

A fix has been deployed for the issue causing intermittent SMS delivery failures in the UAE. We are continuing to monitor the results of the fix at this time.

While we have identified the issue causing intermittent SMS delivery failures in the UAE, we are still waiting for a solution to be provided by the local carriers. We are continuing to monitor the situation closely and will provide updates as they are available. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

We have identified the issue causing intermittent SMS delivery failures in the UAE. Local carriers are experiencing some intermittence. We are continuing to monitor the situation closely and will provide updates as they are available. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

We have identified the issue causing SMS Delivery failures in the UAE and are waiting for our service provider to implement a fix. Please check back here or subscribe to updates for any changes.

We are currently experiencing an issue with SMS Delivery in UAE. we are currently investigating the issue.

## Summary  On February 13, 2025 at 18:00 UTC, some Duo customers experienced an unexpected service disruption, affecting services including:   * Core Authentication Service  * Passwordless Authentication  * Risk-based Authentication  * Telephony Authentication  * Admin Panel logins  * Device Management Portal  * Device Health Policies via Duo Desktop   * New user enrollments  Engineering teams manually restored services around 22:30 UTC. During the outage, no data was lost, and active sessions remained valid.  ## Details    Duo's cloud service is internally implemented by multiple microservice applications, each responsible for a product feature. A service manager takes in a configuration describing each service and automates deploying them to run on cloud infrastructure.  ‌ The issue began with the planned removal of a deprecated application. Due to a bug, after the removal the configuration for service manager’s own application had an error. The manager interpreted this error to mean it should remove itself and all services it manages, instead of removing only the deprecated service.  ‌ Duo SRE received alerts that critical services were no longer running. After diagnosing the problem, Duo SRE redeployed the service manager, followed by all services. This process took several hours because lower-level services \(like network management\) had to be redeployed before features like telephony authentication could run on top of them.  ‌ The bug affects an older version of Duo’s service manager which is responsible for telephony, risk-based authentication, self-service device management, and some passwordless authentication factors. These features were completely unavailable until each one was restored by region.  ‌ This bug did not occur when we removed the deprecated service from any of our staging environments which use the same service manager version.  ‌ Users experienced higher than normal error rates with push and other authentication services as their dependencies recovered. These services run on a newer version of the service manager.  ## What is Duo doing to prevent this in the future?  Duo is removing the ability for removal of one service to automatically remove other service dependencies. Each removal will have to be reviewed and approved individually, even in versions of the service manager that did not have the bug. This prevents the issue from happening again while making service removal more explicit and thus safer.  Duo had prior plans to migrate all services to our newer service manager. In response to this event, we plan to expedite the migration effort.  This new service manager is more reliable and has better isolation to minimize the impact of any potential incidents. It also uses a smaller service mapping eliminating a single point of failure, resulting in a more resilient architecture paradigm than the legacy service manager. Duo will also review Authorization and Scope of Access Control to ensure permissions and control so that changes to one service cannot negatively impact other services.

We can now confirm that all services have been completely restored. A full RCA will be provided as soon as possible. Thank you for your patience, while we worked to resolve the issues.

Device Management Portal services have now been restored for all deployments. We will provide further details as more progress on restoration is made.

Core Authentication services have now been restored for the following deployments: DUO1 DUO2 DUO4 DUO5 DUO6 DUO7 DUO9 DUO10 DUO13 DUO14 DUO15 DUO16 DUO17 DUO18 DUO19 DUO20 DUO21 DUO22 DUO23 DUO24 DUO28 DUO31 DUO33 DUO35 DUO36 DUO37 DUO39 DUO40 DUO41 DUO42 DUO45 DUO49 DUO50 DUO52 DUO55 DUO56 DUO58 DUO60 DUO62 DUO63 DUO64 DUO65 DUO72 DUO73 DUO74 DUO75 DUO76 DUO77 DUO78 DUO79 DUO80 We will provide further details as more progress on restoration is made.

Device Management Portal services have now been restored for the following deployments: DUO1 DUO2 DUO4 DUO5 DUO6 DUO7 DUO9 DUO10 DUO13 DUO14 DUO15 DUO16 DUO17 DUO18 DUO19 DUO20 DUO21 DUO22 DUO23 DUO24 DUO28 DUO31 DUO33 DUO35 DUO36 DUO37 DUO39 DUO40 DUO41 DUO42 DUO45 DUO49 DUO50 DUO52 DUO55 DUO56 DUO58 DUO60 DUO62 DUO63 DUO64 DUO65 DUO72 DUO73 DUO74 DUO75 DUO76 DUO77 DUO78 DUO79 DUO80 We will provide further details as more progress on restoration is made.

We are seeing successful SMS and Phone Call Delivery for the DUO70 deployment. We are still actively working toward restoring all other services and will provide updates as soon as possible.

Telephony services and the Device Management Portal services have now been restored for the DUO38 and DUO48 deployments. We will provide further details as more progress on restoration is made.

We are seeing successful recovery of Admin Panel login for all deployments. We are still actively working toward restoring all other services and will provide updates as soon as possible.

We are seeing successful SMS and Phone Call Delivery for the additional following deployments below. Other deployments not in the list may still be impacted: DUO1 DUO2 DUO4 DUO5 DUO6 DUO7 DUO10 DUO13 DUO14 DUO15 DUO16 DUO18 DUO19 DUO20 DUO21 DUO23 DUO24 DUO28 DUO31 DUO33 DUO35 DUO36 DUO37 DUO41 DUO60 DUO66 DUO68 DUO79 DUO80 We are still actively working toward restoring all other services and will provide updates as soon as possible.

We are seeing successful SMS and Phone Call Delivery for the following deployments below. Other deployments not in the list may still be impacted: DUO9 DUO17 DUO22 DUO39 DUO40 DUO42 DUO45 DUO49 DUO50 DUO52 DUO55 DUO56 DUO58 DUO62 DUO63 DUO64 DUO65 DUO72 DUO73 DUO74 DUO75 DUO76 DUO77 DUO78 We are still actively working toward restoring all other services and will provide updates as soon as possible.

We have identified the issue causing Core Authentication Service, Admin Panel login, Device Management Portal, Risk-based Authentication, and SMS/Phone Call delivery failures across all deployments and are working to deploy a fix. If you have your Admin Panel URL saved, you can navigate to the URL (ex. admin-xxxxxxxx.duosecurity.com/) to get direct access. When accessing the Admin Panel, please utilize non-telephony-based MFA methods to ensure proper access. Admin's currently logged in can activate Duo Push for other admins following this documentation: https://duo.com/docs/administration-admins#updating-an-administrator's-secondary-authentication-methods

We have identified the issue causing Admin Panel login, Device Management Portal, Risk-based Authentication, and SMS/Phone Call delivery failures across all deployments and are working to deploy a fix. If you have your Admin Panel URL saved, you can navigate to the URL (ex. admin-xxxxxxxx.duosecurity.com/) to get direct access. When accessing the Admin Panel, please utilize non-telephony-based MFA methods to ensure proper access. Admin's currently logged in can activate Duo Push for other admins following this documentation: https://duo.com/docs/administration-admins#updating-an-administrator's-secondary-authentication-methods

We are currently investigating an issue causing Admin Panel login and SMS/Phone Call delivery failures across all deployments. If you can access your Admin Panel, please utilize our other MFA methods such as Push, Passcodes, Hardware Tokens, and Security Keys in the meantime. https://duo.com/docs/policy#authentication-methods Please check back here or subscribe to updates for any changes.

We have confirmed that following the rollback of the recent D308 changes for affected customers, Duo SSO authentications are now fully operational, and the issue has been resolved.

We have identified that the issue impacting certain customers originated from the D308 release. We have resolved this by rolling back the deployment and are actively monitoring for any recurrences of the failures.

We have identified that this issue is impacting a specific group of Duo Single Sign-On customers who are not using Duo Passwordless. We are actively working on implementing a solution for those impacted.

We are investigating an issue that is causing some customers to experience authentication failures when logging into applications protected by Duo SSO.

**Summary**  On January 30, 2025, at 10:08am EST Duo's Engineering Team rolled out a planned infrastructure update as part of a capacity planning initiative.  As a result of the changes made in that update one of Duo’s Single Sign-On \(SSO\) servers failed to properly reconnect to one of the necessary components that serves a key role in our authentication path. This led to authentication failures for some of our customers.  Upon being alerted of the incident by impacted customers the Duo team restarted the impacted server and authentications returned to normal. In total, 50 customers were impacted.  **Deployments Impacted**  DUO1  DUO2  DUO4  DUO6  DUO10  DUO13  DUO15  DUO16  DUO18  DUO19  DUO23  DUO28  DUO31  DUO33  DUO36  DUO37  DUO41  DUO60  DUO79 DUO80  **Timeline of Events EST**  2025-01-30 10:08 Duo rolled out a planned infrastructure update.  2023-01-30 12:50 Duo engineering was alerted of multiple customers experiencing SSO authentication failures.  2025-01-30 13:01 Duo engineering ran a restart on the impacted server  2025-01-30 13:11 The service was observed to be fully restored and all SSO authentications were   working again.  **Further Details**  **Customer Impact**  50 Duo SSO customers had at least 1 user that was impacted by this outage.  **What is Duo doing to prevent this in the future?**  Duo Engineering has several planned action items to improve our observability on this specific kind of issue. Our alerting failed to identify us in the timely manner of the issue.  Duo Engineering is also exploring application updates that will prevent reconnection issues like the one experienced during this outage from happening again.  **Customer Suggested Steps**  If you are a Duo SSO customer, please follow the guidance in our [documentation](https://duo.com/docs/sso#configure-your-authentication-source:~:text=We%20recommend%20three%20Authentication%20Proxy%20servers%20for%20high%20availability.) to set up multiple Duo Authentication Proxies for a high availability SSO configuration. We confirmed that customers who used the recommended HA setup were impacted far less than those who did not. While Duo is working to make sure this kind of outage doesn’t happen again, maintaining a high availability setup has proven to help avoid a variety of common failures modes and is therefore still a highly recommended step for all customers using Duo SSO. More information on how to do this can be found in [this Knowledge Base article](https://help.duo.com/s/article/6321). Note: You can find your Duo deployment’s ID and sign up for updates via the Status Page by following the instructions [in this knowledge base article](https://kb.duo.com/s/article/2060).

We can now confirm that SSO authentications are now fully operational and the issue is resolved. We will provide an RCA as soon as it is available. In the meantime, we highly recommend configuring multiple Duo Authentication Proxies, ideally 3, for Duo SSO for redundancy, as only customers who had a single proxy were impacted. More details on this can be found here: https://duo.com/docs/sso#configure-your-authentication-source https://help.duo.com/s/article/6321

We are continuing to monitor for any further issues.

We have implemented a fix and are seeing successful recovery of Duo SSO authentications for impacted customers. We will continue monitoring to ensure the issue is fully resolved.

We are investigating an issue that is causing a small number of customers to experience authentication failures when logging into applications protected by Duo SSO.

**Summary** On January 28, 2025, at around 18:45, Duo's Engineering Team was alerted by monitoring that indicated errors observed in the DUO69 MFA deployment. The root cause was identified as an incomplete configuration update rollout in the environment, resulting in the deployment becoming unhealthy. The issue was fully resolved on the same day by 19:55. ‌ **Timeline of Events** 2025-02-28 18:45 Duo's Engineering Team is alerted by monitoring that indicated errors in the DUO69 deployment. SRE begins triage. 2025-02-28 19:06 All the nodes for DUO69 deployment were identified as being in \`NotReady\` state. 2025-02-28 19:07 Authentication impact for this deployment was identified as 100%. 2022-02-28 19:41 A review of recent changes to the system identified that a change previously made had not completed successfully and was the root cause of the failure. 2022-02-28 19:42 The root cause was fixed by executing the system change to completion. 2022-02-28 19:47 All nodes for this deployment were up and healthy. ‌ **Details** The Duo Site Reliability Engineering Team has been rolling out changes to the way that engineers access the Amazon Elastic Kubernetes Service \(EKS\) clusters, moving from an older deprecated method to using access entries as recommended by AWS as a best practice. During the rollout, the IAC \(Infrastructure-as-Code\) tooling needed to perform an operation that affected permissions for services in the cluster. The IAC tool saw the need to detach and reattach a policy although this was unnecessary. The order of operations caused the policy to remain detached. This resulted in the infrastructure and services being unable to authenticate with our EKS cluster and nodes could not join the cluster or renew their leases defaulting to a ‘NotReady’ state ultimately caused the system outage. Although the initial results appeared successful, the permissions were not applied correctly. Subsequently re-running our IAC tool resolved this issue by reattaching the policy and allowing the services to authenticate with the EKS cluster. ‌ **How did Duo Resolve the incident** Once the issue had been identified, re-running our IAC tooling completed the partial changes, allowing for Kubernetes nodes to authenticate to the cluster, reach a Ready state and have resources scheduled onto them again that could process authentication traffic and restore service. ‌ **How many Customers were impacted, if applicable** This incident affected all customers on the DUO69 deployment. ‌ **What is Duo doing to prevent this in the future?** As this is a one-time change, this issue is not expected to occur again in the future. However, Duo has added some automation to the IAC change process to ensure that such incidents are not repeated. We have also updated our production change process to include a stricter review when changes are made to production clusters.

The issue causing authentication failures in the India region has been resolved and full functionality has been restored.

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

We have identified the issue causing authentication failures including passwordless experience in the India region and a fix is being implemented. Please check back here or subscribe to updates for any changes

We are currently investigating an issue causing authentication failures including passwordless experience in the India region and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

The issue causing intermittent phone call delivery failures in the UK region has been resolved and full functionality has been restored.

We have identified the issue causing intermittent phone call delivery failures in the UK region and have deployed a workaround. We are monitoring the the results of the fix at this time.

We have identified the issue causing intermittent phone call delivery failures in the UK region. Local carriers are experiencing some intermittence. We are monitoring the situation closely and will provide updates as they are available. During this time, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Tokens etc to login to your Duo-protected integrations.

We are currently investigating an issue causing intermittent phone call delivery failures in the UK region. While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc to login to your Duo-protected integrations. Please check back here or subscribe to updates for any changes.

**Summary** On January 7, 2025, Duo's Engineering Team mitigated a log delay for certain admin panel users. The root cause was identified an incorrect software deployment. The issue was resolved on the same day by deploying the correct version of software for activity and telephony logs. **Details** During our regular patch cycle, an incorrect version of the software was inadvertently pushed to the production instances. The issue was quickly identified, and the team immediately rectified it by deploying the correct version to the newly patched instances. The response aimed to minimize potential impact and ensure that the correct functionality was restored without significant downtime. Multiple teams worked together to ensure the integrity of the deployments and restore system stability. We promptly triaged the environment to identify affected deployments and pushed the correct software versions to each one. After deploying the updates, we conducted thorough verification to ensure both the correct software version and the appropriate patch version were in place. The patching process is currently in its final evolution phase following our recent transition to Auto Scaling Groups \(ASGs\). Moving forward, each team will be responsible for managing their deployments patching to minimize external interference with their regular release schedules, which occur at least every two weeks and thus still adhere to our compliance guidelines on vulnerability management. This approach will streamline operations and ensure greater autonomy for teams while maintaining system stability.

The issue impacting the availability of Activity and Telephony Log messages in the Admin Panel / Admin API is now resolved and full functionality has been restored.

We have implemented a fix for the issue impacting the availability of Activity and Telephony Log messages in the Admin Panel / Admin API. We will continue to monitor and post any updates when the incident is considered fully resolved.

We have identified the issue impacting the availability of Activity and Telephony Log messages in the Admin Panel / Admin API and are working to deploy a fix.

We are currently investigating an issue that is impacting the availability of Activity and Telephony Log messages for the following deployments below. This impacts the Admin Panel and Admin API: DUO9 DUO17 DUO22 DUO39 DUO40 DUO42 DUO45 DUO50 DUO52 DUO55 DU056 DUO58 DUO61 DU062 DU063 DU064 DU065 DU072 DUO73 DUO74 DU075 DUO76 DUO77 DUO78 Authentication and all other functionality is operational. We are actively working toward resolving this issue, and will provide further details as soon as they are available.

The issue with call handling for our Duo Support Team has been resolved.

We have identified an issue with Phone Support availability for our Duo Support Team and are working to deploy a fix. If you need to submit a case, please utilize the Duo Support Portal or send us an email to support@duo.com

After further investigation, we have confirmed that no customers should be impacted by this, as only internal systems were impacted. This issue is now Resolved, and further enhancements to ensure reliability and corresponding alerting adjustments will be made moving forward.

We are investigating issues with intermittent failures retrieving SSO logs when attempting to view them in the Admin Panel and/or through the Admin API for customers on the deployments below. This does not impact authentication. DUO38 DUO47 DUO57 DUO66 DUO67

The issue causing SMS delivery failures for some Australian customers is now resolved and full functionality is restored.

The affected carrier has implemented a fix for the issue causing SMS delivery failures for some Australian customers. We will continue to monitor the issue and will post any updates when the incident is considered fully resolved.

We have identified the cause of the SMS delivery failures for some Australian customers as a carrier issue and our SMS providers are working with the carrier to restore service.

We are currently investigating an issue causing SMS delivery failures for some Australian customers on all of our deployments and are working to correct the issue as soon as possible. While we investigate this, please use alternate authentication methods such as Duo Push, Duo Mobile Passcodes, Hardware Token etc to login to your Duo-protected integrations. Please check back here or subscribe to updates for any changes.

**Summary**  On Nov 4, 2024, between 6:37 p.m. and 7:20 p.m. ET, FedRAMP customers using YubiKey tokens for authentication experienced failed authentications. The root cause was identified as a configuration error introduced during the rollout of a new software version for the internal proxy service.  **Deployments Impacted**  * DUO61  **Timeline of Events \(ET\)**  * **2024-11-04 6:38:35** - Duo Site Reliability Engineering \(SRE\) is alerted by an automated monitoring system of a high number of Python tracebacks.  * **2024-11-04 7:05:00** - The issue is identified as related to the recent software upgrade to the internal proxy service.  * **2024-11-04 7:11:00** - The software rollback process is initiated.  * **2024-11-04 7:20:00** - Rollback process completes, and Python tracebacks decrease.  * **2024-11-04 7:22:00** - The Duo status page is updated to inform customers of the downtime.  **Details**  The root cause was identified as a configuration mismatch between two services, introduced during the new software deployment. The issue was identified and resolved within 40 minutes, impacting 494 users.  As a short-term solution, Duo rolled back to the previous stable version of code to mitigate customer impact. After authentications were confirmed to be successful again, Duo released a permanent fix to the affected deployments to ensure long-term stability.

The issue causing authentication failures using Yubikey tokens 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.

We have implemented a fix for the authentication issue using Yubikey tokens. We will continue to monitor the issue and will post any updates when the incident is considered fully resolved.

We have identified the cause of the authentication issue using Yubikey tokens and are actively working to restore service.

We are currently investigating an issue that is affecting authentication using Yubikey tokens on Federal Deployments. We are working on remediation and will provide more updates as soon as we have more information.

The issue impacting querying activity and telephony logs via the Duo Admin API and Admin Panel is now resolved and full functionality has been restored.

We have implemented a solution for the issue affecting querying activity and telephony logs and we will continue to monitor and post any updates when the incident is considered fully resolved.

We have identified an issue that affects querying activity and telephony logs via the Duo Admin API and Admin Panel. We are working to deploy a fix at this time. Authentication logs and sign-ins are not impacted.

We are currently investigating an issue that affects access of activity and telephony logs via the Duo Admin API. Authentication logs and sign-ins are not impacted. Please check back here or subscribe to updates for any changes.

The issue impacting the availability of some Duo logs is now resolved and full functionality has been restored. Authentication logs were not impacted

We have implemented a solution for the issue affecting some Duo logs and we will continue to monitor and post any updates when the incident is considered fully resolved.

We have identified the cause of the issue affecting some Duo logs and are working on a fix. Authentication logs are not impacted. We will provide more updates as soon as we have more information. Authentications are not impacted.

We are currently investigating an issue that is affecting some Duo logs. Authentication logs are not impacted. We are working on remediation and will provide more updates as soon as we have more information. Authentications are not impacted.

The incident on DUO78 has now been resolved. No authentications were impacted during the course of this incident.

We have implemented a fix for the issue and can confirm that no authentications were impacted. We continue to monitor it closely and will post a further update when the incident is considered fully resolved.

We have identified the issue on this deployment and confirmed that there is no impact to authentications. We have implemented a fix and will continue to monitor the results at this time.

We are currently investigating an issue causing authentication failures on DUO78. We are working to fix the issue as soon as possible. Please check back here or subscribe to updates for any changes.

Duo Admin Panel logins continue to be successful and all services are fully operational. This incident is resolved.

After continuous testing on our side, we are confident that the issues were short-lived and transient in nature. We are continuing to monitor for any potential uptick in failure rates for Admin Panel logins and will provide updates if/when available.

We are currently investigating an issue causing an error when logging into the Duo Admin Panel. Please check back here or subscribe to updates for any changes.

We can confirm the issues with automated Directory Syncs are now resolved. Some customers' syncs were running more frequently than expected due to this issue. Some of these customers may notice one scheduled sync occurrence being skipped after the fix has rolled out, due to syncs having run too recently. Scheduled syncs will resume as normal following that. Other customers may have observed that their scheduled sync had not occurred at their scheduled times in the last few days, and those syncs will now continue as scheduled.

We have implemented a fix that is rolling out and are observing success for customers who have received it so far. We will continue to monitor the results to confirm this issue is resolved for all customers affected.

We have identified the issue regarding automated directory sync frequency intervals and are working on a fix.

We are investigating an issue that is affecting the frequency of automated Directory Syncs running for some customers, and will provide an update as soon as possible. All other authentication functionality and Admin Panel access remains unaffected. Manual Syncs also continue to function as expected.

### Summary On September 19, 2024, at around 14:08 ET, Duo's Engineering Team was alerted by monitoring that admins on select deployments were unable to retrieve their logs through the Admin Panel or Admin API. The root cause was identified as a configuration issue. The issue was resolved on the same day by rolling back the configuration issue and releasing a permanent fix that addressed the error. ### Timeline of Events ET 14:08 Duo Engineering is informed by monitoring of potential admin panel log delivery failures. 14:14 Duo Engineering creates an incident and escalates to the owning team. 14:15 Owning team begins to troubleshoot. 14:32 Root cause is identified.  15:03 Team decides to rollback the release to mitigate customer facing log delays. 15:12 Impacted deployments begin to recover. 15:23 Team introduces the permanent fix and releases to the impacted deployments. ### Details Our Engineering team was working on enhancing our identity threat insights and decided to pre-configure regions that are planned for future improvements. However, the pre-configuration was based on an incorrect assumption about the underlying infrastructure, which had not yet been built out. As a short-term solution, Duo rolled back to the previous stable version of code to mitigate customer impact. After admins were able to view their logs again, Duo released a permanent fix to the affected deployments to ensure long-term stability.

The issue with Reports and log API performance and consistency have been resolved. An RCA will be provided as soon as it is available.

We are continuing to monitor for any further issues.

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

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

We are investigating an issue causing some reports and/or log APIs to fail to load or show incorrect data across multiple deployments. Please check back for further updates.

Access to the Directory Sync page within the Admin Panel has been fully restored.

We have implemented a fix to restore access to the Directory sync page within the Duo Admin Panel and are currently monitoring the situation to ensure continued access.

Our investigation of the reported directory sync failures show that they are related to accessing the Directory sync page within the Duo Admin Panel. We can confirm that directory syncs themselves are not impacted. We have identified the issue and will be working to restore access to the Directory Sync page in the Duo Admin Panel.

We are currently investigating an issue causing directory sync failures within the Duo Admin Panel across multiple deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

The intermittent issues causing connectivity issues on Duo deployment in Canada has been resolved.

The intermittent issues causing connectivity issues on Duo deployment in Canada has been resolved.

We are monitoring intermittent issues causing connectivity issues on Duo deployment in Canada.

Duo Authentications continue to be successful and all services are fully operational. This incident is resolved.

After continuous testing on our side, we are confident that the issues experienced were caused by external factors. We are continuing to monitor for any potential uptick in failure rates for Duo Authentication and will provide updates when available.

We are investigating an issue causing degraded performance of authentications across multiple Duo deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

Following a period of monitoring, we have confirmed that the authentication issues impacting DUO19 are now fully resolved.

We have identified an issue affecting authentication on DUO19 and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

The SMS delivery issue has been resolved, and all services are fully functional.

We are investigating an issue with SMS Delivery. Please check back for further updates.

The issue regarding authentication failures using Duo Push on multiple deployments is fully resolved and all services are now fully functional.

After investigating, we have determined that our services are fully operational, and we have determined the root cause to be related to a internet service provider outage and isolated to Optus.

After investigating, we have determined that our services are fully operational, and we have determined the root cause to be related to a internet service provider outage and isolated to Optus.

The issue causing SMS passcode authentication failures is now resolved and full functionality is restored.

The issue causing SMS passcode delivery failures for UK numbers is now looks to be resolved now but we will continue to monitor the issue and will post any updates when the incident is considered fully resolved.

We are currently investigating an issue causing SMS delivery to UK numbers and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

The issue causing degraded performance with Duo's authentication service and Admin Panel access is now resolved and full functionality is restored.

We have identified the cause of degraded performance with Duo's authentication service and Admin Panel access and have implemented a fix. We will continue to monitor the results of the fix at this time.

### Summary On August 13 2024, at approximately 10:30 am ET, Duo's Site Reliability Engineering Team received an alert indicating that users on DUO1 were experiencing latency issues. The team identified the root cause as a large and distributed burst of authentication traffic. Duo resolved the issue by 12:12pm ET. ### Deployments Impacted * DUO1 ### Timeline of Events \(ET\) 2024-08-13 10:30am  Duo Site Reliability Engineering \(SRE\) Team receives initial alert regarding DUO1. Engineers begin to investigate the customer impact. 2024-08-13 10:49am Duo SRE Team identifies a large and distributed burst of authentication traffic from a handful of users impacting Duo’s capacity to process authentications. 2024-08-13 11:04am Status page is updated to investigating. 2024-08-13 11:09am Duo SRE Team starts working on multiple solutions to address the degradation, including scaling the infrastructure and mitigating the burst of traffic. 2024-08-13 11:29am Duo SRE Team completes scaling DUO1. 2024-08-13 11:40am Duo SRE Team stops the surge of traffic. Duo SRE begins to monitor systems for recovery. 2024-08-13 12:12pm Incident status updated to resolve after recovery was verified. ### Details Duo Engineering determined that the root cause was a substantial surge in authentication traffic, which impacted Duo's ability to process authentications efficiently. This led to increased latency, triggering our automated back pressure systems to reject requests exceeding a certain threshold to maintain system functionality. As a result, we were able to continue processing the majority of authentications and limit impact to a small percentage of our total user base on this deployment. Duo's Site Reliability Engineering \(SRE\) team conducts capacity planning for deployments based on historical data and expected utilization, ensuring there is sufficient headroom for increased authentication traffic. However, the recent traffic surge exceeded these margins and required manual intervention. The team implemented two solutions: vertically scaling DUO1 to create additional headroom and reduce pressure, and identifying and blocking the traffic sources. These actions successfully reduced the load on DUO1 and resolved the latency issues. During the incident retrospective, the Duo SRE team identified several solutions to prevent similar issues in the future. The solutions include, migrating customers with higher authentication volumes to separate deployments, further optimizations and automation in our scaling of deployments to improve their ability to handle large bursts of traffic, and automating surging authentication traffic mitigation processes.

The issue causing degraded performance with Duo's authentication service 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.

We have implemented a fix for the issue causing degraded performance with Duo's authentication service. We will continue to monitor the issue and will post any updates when the incident is considered fully resolved.

We have identified the cause of the degraded performance with Duo's authentication service and are actively working to restore service to full capacity.

We are continuing to investigate this issue.

We are currently investigating an issue causing degraded performance with the Duo Core Authentication Service on our DUO1 deployment and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

The issue causing degraded performance with Duo's authentication service is now resolved and full functionality is restored.

We have identified the cause of the degraded performance with Duo's authentication service and have implemented a fix. We will continue to monitor the results of the fix at this time.

We are currently investigating an issue causing degraded performance with the Duo Core Authentication Service on our DUO34, DUO,43, and DUO51 deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

### Summary On July 25, 2024, between 12:00 and 12:02 ET, customers on select deployments experienced failed authentications. The short window of downtime resulted in retries that would allow users to successfully authenticate. The root cause was identified as a spike in database contention that was resolved as performance normalized.  ### Deployments Impacted * DUO1, DUO55, DUO56, DUO60, DUO62 & DUO78 ### Timeline of Events ET 2024-07-25 12:05 Duo Site Reliability Engineering \(SRE\) is informed by automated monitoring system of a spike in database contention indicating potential authentication failures.  2024-07-25 12:07 Automated monitoring self-resolves. 2024-07-25 12:35 Initial investigation suggests that a single customer was affected.     2024-07-25 12:37 Further investigation reveals that a small number of customers across multiple deployments were affected.   2024-07-25 12:55 The Duo status page is updated to inform customers of the downtime.  ### Details The root cause was a significant reduction in database Input/Output operations per second \(IOPS\) over a span of 90 seconds. IOPS are provisioned and provided as compute resources by our cloud provider. A reduction in IOPS availability can occur because of workload demand, exceeding provisioned limits, or from a networking or hardware-related issue. The Duo SRE team was unable to find or isolate any internal issue that would have contributed to this incident.  We were able to determine that a single spike was evident after the IOPS was momentarily halted, and we are working with our vendor to ensure better transparency if such an issue occurs in the future.   The issue was resolved within 90 seconds, as database performance normalized.

At approximately 4pm UTC, we experienced brief outage that caused authentication failures on deployments DUO1, DUO55, DUO56, DUO60, DUO62, DUO78. The issue has since been resolved. We will provide an RCA as soon as it is available.

The issue regarding phone call authentication for India on all of our deployments has been resolved.

We are now seeing consistent success with our phone call authentications from India and we will continue to monitor the results.

We have identified the cause of the phone call authentication failures for India are related to an external carrier.

We are currently investigating a degraded state for calls in India.

The issue with call handling for our Duo Support Team has been resolved.

We have deployed a fix for the issue with call handling for our Duo Support Team and are monitoring the results.

We have identified the issues with call handling for our Duo Support Team and are working to deploy a fix. If you need to submit a case, please utilize the Duo Support Portal or send us an email to support@duo.com

We are currently investigating an issue with call handling for our Duo Support Team. If you need to submit a case, please utilize the Duo Support Portal or send us an email to support@duo.com Please check back here or subscribe to updates for any changes.

### Summary On July 22, 2024, from 4:38 pm ET to 4:40 pm ET, users on DUO15 experienced a brief authentication outage. The root cause was identified as a configuration issue with one of our Deployment Services. The issue was resolved in approximately 2 minutes, as the services came online again. ### Deployments Impacted * DUO15 ### Timeline of Events EST 2024-07-22 14:03: Duo Site Reliability Engineering \(SRE\) is informed that the Continuous Delivery system is not working as expected  2024-07-22 14:11: SRE acknowledges that updates are not propagating to production systems via Continuous Delivery system   2024-07-22 14:13: SRE decides that for quick propagation of updates to production systems, a manual restart is needed 2024-07-22 14:14: SRE starts manually upgrades across various deployments and it was observed that changes were propagating as expected.   2024-07-22 16:38: While upgrading one deployment in a similar fashion, SRE observed that all the services were terminated during rolling restarts, resulting in a downtime of about two minutes 2024-07-22 16:40: New services in the affected deployment start serving traffic with updated configurations 2024-07-22 16:45: To avoid such scenarios in the rest of the deployments, SRE decided that the safest way was to take down one service at a time while the others served incoming traffic. 2024-07-22 17:30: All the deployments were updated with latest configuration changes 2024-07-22 22:30: SRE identified the root cause of Continuous Delivery System not working as expected and proceeds to solve the issue. ### Details During a scheduled configuration rollout, the team noticed that our Deployment Service was struggling with a specific Deployment. The team quickly noticed this issue and moved to remediate it.  However, while doing so, there was a brief outage of our Core Authentication Service affecting the DUO15 deployment.  The team diligently deployed the rest of the configurations one by one, to ensure we followed the 33% restart per deployment guidelines. 800-1000 authentications were affected. **To ensure that this issue doesn’t happen again, we’ve done the following:**  1. Added steps to make sure manual intervention is not needed/as minimal as possible. 2. If manual intervention is ever needed, make sure to take the services out one by one.

From approximately 8:37 AM UTC to 8:40 AM UTC, there was a brief outage of our Core Authentication Service affecting the DUO15 deployment. All services are now fully functional and we are working to provide a Root Cause Analysis as soon as it is available.

The issue regarding SMS passcode authentication failures for India on all of our deployments has been resolved.

We have deployed a fix for the issue causing SMS passcode authentication failures for India on all of our deployments and are monitoring the results.

We have identified the issues causing SMS passcode authentication failures for India on all of our deployments and working on deploying a fix.

We are currently investigating an issue causing SMS passcode authentication failures for 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.

We have resolved the issue impacting the support phone number listed on duo.com/support.

We have identified the issue with reachability to the phone number listed on Duo's Support Page and are working towards a resolution. As a workaround, please use the phone number found in your Duo Admin Panel under the Help menu in the top right corner of the page.

We are currently investigating an issue with reachability to the phone number listed on Duo's Support Page. As a workaround, please use the phone number found in your Duo Admin Panel under the Help menu in the top right corner of the page.

We have received confirmation from our provider that all residual issues with Trusted Endpoint certificate generation and management system creation are now also resolved. All Duo services are fully functional.

We have reviewed the current situation and can confirm that Duo services remain fully operational and continuing to monitor for any further issue. We are unable to provide any status related updates for the external issues.

We are continuing to monitor for any further issues and can confirm that Duo services remain fully operational. We are unable to provide any status related updates for the external issues.

We are currently monitoring multiple customer reports indicating connectivity issues with Duo services and believe this is related to current external issues. We confirm that Duo's services remain fully operational, provided that a stable network route is maintained, and we are unable to issue or renew certs for Trusted Endpoints. We also recommend reaching out to your ISP for assistance and checking their status page for the latest updates on this matter.

We are currently monitoring multiple customer reports indicating connectivity issues with Duo services and believe this is related to current external issues. We confirm that Duo's services remain fully operational, provided that a stable network route is maintained. We also recommend reaching out to your ISP for assistance and checking their status page for the latest updates on this matter.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We are currently conducting a thorough investigation into multiple customer reports indicating connectivity issues with Duo services, specifically from users with certain Internet Service Providers (ISPs). Preliminary findings suggest that these issues may originate from a peering provider utilized by several of these ISPs. Our team is actively working to gather more information and will issue further updates as soon as additional details become available. We confirm that Duo's services remain fully operational, provided that a stable network route is maintained. We also recommend reaching out to your ISP for assistance and checking their status page for the latest updates on this matter.

The issues regarding SMS Message Delivery issues due to telephony carrier service issues in the India region are fully resolved and all services are now fully functional.

After investigating, we have determined that our services are fully operational, and the root cause of the SMS failures to India to be related to a carrier outage.

We are currently investigating an issue causing SMS passcode authentication failures for 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.

After reviewing the issues reported, this issue is being caused by carrier disruptions. For further assistance on this, please consider contacting your carrier. We will continue to monitor.

We are monitoring the issue that has been impacting push delivery.

After investigating, we have determined that our services are fully operational, and we have determined the root cause to be related to a carrier outage and isolated to Verizon Networks.

We are currently investigating issues regarding Duo Push Authentications not arriving at user devices.

Between 20:50 and 21:10 EDT on July 12, 2024, authentication logs were delayed in being updated in the Duo Admin Panel in the below deployments. DUO1, DUO2, DUO4, DUO5, DUO6, DUO7, DUO10, DUO13, DUO14, DUO15, DUO16, DUO18, DUO19, DUO20, DUO21, DUO23, DUO24, DUO28, DUO31, DUO33, DUO35, DUO36, DUO37, DUO41, DUO60, DUO79 and DUO80 Authentications were not impacted and the delayed logs have since been processed and are available in Duo Admin Panel and via Duo API.

We have resolved the issue impacting the support phone number listed on the Duo Admin Panel, as well as the Federal and VIP phone numbers.

We have identified the issue impacting the support phone number listed on the Duo Admin Panel, as well as the Federal and VIP phone numbers and are working towards a resolution. As a workaround, please use our other regionalized numbers found at https://duo.com/support or send an email to support@duo.com.

We are currently investigating an issue with reachability to the phone number listed on Duo's Admin Panel, as well as the Federal and VIP phone numbers. As a workaround, please use our other regionalized numbers found at https://duo.com/support or send an email to support@duo.com.

We have resolved the delay in displaying new authentication logs in the Duo Admin Panel. Logs impacted during the incident are available and we can confirm no logs were lost.

We have resolved the delay in displaying new authentication logs in the Duo Admin Panel. We are currently monitoring log data to confirm no logs were lost.

We have identified an issue causing delays and failures to load Authentication Logs from the Duo Admin Panel and are working to deploy a fix. Please subscribe to the status page for further updates.

The issue causing intermittent authentication failures on our DUO13 deployment has been resolved. We will be posting a root-cause analysis (RCA) here once our engineering team has finished its thorough investigation of the issue.

We have identified the issues causing intermittent authentication failures on our DUO13 deployment and have deployed a fix. We are monitoring the results of the fix at this time.

We have identified the issues causing intermittent authentication failures on our DUO13 deployment and are working to deploy a fix.

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

The issue causing intermittent Passwordless authentication failures on DUO79 has been resolved. We will be posting a root-cause analysis (RCA) here once our engineering team has finished its thorough investigation of the issue.

We have identified the issue and deployed a fix for the intermittent Passwordless Authentication failures on DUO79. We are continuing to monitor the impact of the fix at this time.

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