# \[DUO34\] Full Deployment Outage

- Provider: [Duo Security](https://down.guide/duo)
- Level: confirmed
- Impact: Major outage
- lasted 43m
- started 2025-10-07 19:13 UTC
- Core Authentication Service, Admin Panel, Push Delivery +2
- id: DWN-479fa83bd7
- Official page: https://stspg.io/wq4v1sjz9rl4

## Updates from Duo Security
### 2025-10-07 19:13 UTC: investigating
We are currently investigating an issue causing a full outage for all services on our DUO34 deployment and are working to restore services as soon as possible.
Please check back here or subscribe to updates for any changes

### 2025-10-07 19:23 UTC: identified
We have identified the issue causing an outage for all services on our DUO34 deployment and working to deploy a fix.

### 2025-10-07 19:44 UTC: monitoring
We have deployed a fix for the issue causing an outage for all services on our DUO34 deployment and are monitoring the results at this time.

### 2025-10-07 19:56 UTC: resolved
The issue causing an outage for all services on our DUO34 deployment has been resolved.
We will publish a RCA as soon as it is available. You can check back here for the latest information or subscribe for updates.

### 2025-10-09 14:04 UTC: postmortem
# \*\*DUO34 Deployment Outage\*\* 
## Incident Report – 10/7/2025 
### Summary 
On October 7, 2025, between 2:40pm EDT and 3:40pm EDT, all services on Duo 34 were unavailable. This was due to a misconfiguration in our edge load balancer which stopped all traffic to that deployment. Duo engineering promptly fixed the misconfiguration and have fixed the underlying cause, to ensure our systems are more resilient. 
### Details 
Duo’s application platform has two parts to manage our services. One-part handles creating the network setup, and the other controls how traffic reaches running services. A service disruption occurred because of a misalignment between these two key systems. Even though the network was set up correctly, changes were not reflected in the traffic routing settings. This caused traffic to stop reaching the services, resulting in the outage.   
To restore service, a manual fix was put in place to connect these network servers with the right settings. As a long-term solution, we have updated the system settings to point to the right destinations. This will ensure that the misalignment will not happen again. To avoid this problem in the future, we're reviewing how we manage system configurations, improving our setup process to avoid local files, and adding checks to stop changes that could cause similar issues.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).