User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
duo.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 777 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 602 ms | 0 |
| 03:30 | 0 | 0.0 | 515 ms | 0 |
| 03:45 | 0 | 0.0 | 904 ms | 0 |
| 04:00 | 0 | 0.0 | 391 ms | 0 |
| 04:15 | 0 | 0.0 | 338 ms | 0 |
| 04:30 | 0 | 0.0 | 275 ms | 0 |
| 04:45 | 0 | 0.0 | 360 ms | 0 |
| 05:00 | 0 | 0.0 | 334 ms | 0 |
| 05:15 | 0 | 0.0 | 607 ms | 0 |
| 05:30 | 0 | 0.0 | 681 ms | 0 |
| 05:45 | 0 | 0.0 | 274 ms | 0 |
| 06:00 | 0 | 0.0 | 451 ms | 0 |
| 06:15 | 0 | 0.0 | 518 ms | 0 |
| 06:30 | 0 | 0.0 | 372 ms | 0 |
| 06:45 | 0 | 0.0 | 306 ms | 0 |
| 07:00 | 0 | 0.0 | 672 ms | 0 |
| 07:15 | 0 | 0.0 | 486 ms | 0 |
| 07:30 | 0 | 0.0 | 292 ms | 0 |
| 07:45 | 0 | 0.0 | 513 ms | 0 |
| 08:00 | 0 | 0.0 | 1339 ms | 0 |
| 08:15 | 0 | 0.0 | 384 ms | 0 |
| 08:30 | 0 | 0.0 | 827 ms | 0 |
| 08:45 | 0 | 0.0 | 326 ms | 0 |
| 09:00 | 0 | 0.0 | 361 ms | 0 |
| 09:15 | 0 | 0.0 | 424 ms | 0 |
| 09:30 | 0 | 0.0 | 1335 ms | 0 |
| 09:45 | 0 | 0.0 | 726 ms | 0 |
| 10:00 | 0 | 0.0 | 496 ms | 0 |
| 10:15 | 0 | 0.0 | 266 ms | 0 |
| 10:30 | 0 | 0.0 | 706 ms | 0 |
| 10:45 | 0 | 0.0 | 264 ms | 0 |
| 11:00 | 0 | 0.0 | 327 ms | 0 |
| 11:15 | 0 | 0.0 | 255 ms | 0 |
| 11:30 | 0 | 0.0 | 388 ms | 0 |
| 11:45 | 0 | 0.0 | 1190 ms | 0 |
| 12:00 | 0 | 0.0 | 213 ms | 0 |
| 12:15 | 0 | 0.0 | 482 ms | 0 |
| 12:30 | 0 | 0.0 | 615 ms | 0 |
| 12:45 | 0 | 0.0 | 347 ms | 0 |
| 13:00 | 0 | 0.0 | 346 ms | 0 |
| 13:15 | 0 | 0.0 | 301 ms | 0 |
| 13:30 | 0 | 0.0 | 541 ms | 0 |
| 13:45 | 0 | 0.0 | 244 ms | 0 |
| 14:00 | 0 | 0.0 | 337 ms | 0 |
| 14:15 | 0 | 0.0 | 435 ms | 0 |
| 14:30 | 0 | 0.0 | 591 ms | 0 |
| 14:45 | 0 | 0.0 | 1409 ms | 0 |
| 15:00 | 0 | 0.0 | 777 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Duo Security yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Duo Security goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Duo Security alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Duo Security is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Duo Security's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.