[Multiple Deployments] Admin Panel Login Failures

What to do

• Check whether you use Duo Security Admin Panel, Admin Panel, Admin Panel, Admin Panel and 75 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 26m it lasted.

  Anything that failed between 2025-09-09 16:43 UTC and 2025-09-09 17:09 UTC may need a replay.

• Subscribe to Duo Security's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=duo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Duo Security 4

1. identifiedSep 9, 2025, 4:44 PM 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.

   provider

2. monitoringSep 9, 2025, 4:54 PM 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.

   provider

3. resolvedSep 9, 2025, 5:09 PM 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.

   provider

4. postmortemSep 10, 2025, 9:27 PM 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 reverted the change to restore service and resolve the issue. ### Details On September 9, Duo engineering executed a planned integration of two services related to the admin panel and billing. This integration aimed to reduce database load and address infrequent internal errors. Although the change was tested in lower environments, it was incompatible with the production region it targeted, causing issues when deployed in production. Duo engineering promptly began reverting the change to address the errors and minimize customer impact. On the same day, the team implemented a fix to resolve the configuration incompatibilities. Moving forward, Duo is enhancing our testing processes to identify incompatibilities before implementing approved changes and to reduce downtime for our customers. We apologize for any disruption this may have caused.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.