# New builds might take longer to start serving traffic

- Provider: [Deno Deploy](https://down.guide/providers/deno-deploy)
- Confidence: Confirmed
- Impact: Degraded
- lasted 0m
- started 2026-04-24 10:00 UTC
- Console, Managed Network
- id: DWN-0678ff3842
- Official page: https://denostatus.com/incident/cmogyd6cw19ucsu8ac6xdpyl9

## Updates from Deno Deploy
### 2026-04-24 10:00 UTC: resolved
Type: Incident
 Duration: 3 days, 2 hours and 24 minutes
 Affected Components: Console, Managed Network
 Apr 27, 12:23:32 GMT+0 - Resolved - This incident has been resolved. Apr 24, 10:00:00 GMT+0 - Identified - Users are experiencing that new builds are not immediately serving traffic after deployment and that traffic continues being served by the previous build.
We're currently working on a fix for this issue.

From the builder: does your app depend on Deno Deploy? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=deno-deploy) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Deno Deploy.

---
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://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-0678ff3842), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.