CHYP.ai · ORBIT // Cloudy_Day Security Suite

Identity, access & networking

Operational Duo Security status

duo.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Duo Security looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.

confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Core Authentication Service

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started78 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Duo - Partial Hardware Token Authentication Issues - United States”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Duo Security may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Duo Security's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.

Who depends on whom

Duo Security may run on Amazon Web Services (inferred). We don't map other services that depend on Duo Security. Dependency chains are where single points of failure hide.

Identity & trust lens

When Duo Security has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Duo Security or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Duo Security. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Duo - Partial Hardware Token Authentication Issues - United States

minor resolved · started · resolved

3 updates

  1. investigating

    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 expected to succeed. Other Duo authentication methods are not expected to be impacted and can be used as alternate methods if configured and available. Our engineering team is actively investigating and has started mitigation steps. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

  2. monitoring

    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 succeed. Other Duo authentication methods are not expected to be impacted and can be used as alternate methods if configured and available. We will continue to monitor service stability and provide additional updates as needed.

  3. resolved

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

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next