Skip to main content
Duo Security

Duo Phone Call Authentication Failure for US Based Carriers

Degraded Lasted 3h 15m · started · Duo Security's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
24of 100

What to do

  • Check whether you use Duo Security in us. 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 3h 15m it lasted.

    Anything that failed between 2026-03-22 17:18 UTC and 2026-03-22 20:33 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. investigating

    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 list of all other alternative authentication methods can be found here: https://duo.com/docs/policy#authentication-methods Please check back here or subscribe to updates for any changes.

    provider

  2. investigating

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

    provider

  3. monitoring

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

    provider

  4. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-a34009667a

Is Duo Security still down?

No, this incident was resolved 2026-03-22 20:33 UTC. For Duo Security's live state, see https://down.guide/duo.

How long did it last?

3h 15m, from 2026-03-22 17:18 UTC to 2026-03-22 20:33 UTC, by the times Duo Security posted.

What was affected?

Duo Security named in us.

What caused it?

Duo Security hasn't published a root cause. If it does, it shows here.

Where does this come from?

Duo Security's official status page, https://status.duo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.