Deno Deploy incident
Deno Deploy Chicago cluster outage
Deno Deploy experienced a major incident on July 3, 2026 affecting Deno Deploy (Managed Network) and Websites (deno.land) and 1 more component, lasting 2h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 03, 2026, 12:07 AM UTC
Starting around 00:07 UTC, the Deno Deploy Chicago cluster is unreachable. This affects the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they may be affected as well. The Deno Deploy console remains available, but builds triggered via GitHub integration, CLI, or API may fail because builds run in Chicago. Sandbox creation in Chicago may also fail. We are investigating.
- investigating Jul 03, 2026, 12:23 AM UTC
We are continuing to investigate a major outage affecting deno.com, deno.land, and Deno Deploy managed network traffic. Builds triggered via GitHub integration, CLI, or API may also fail because builds run in Chicago. Sandbox creation in Chicago may also fail.
- identified Jul 03, 2026, 12:34 AM UTC
We have identified the cause as a Vultr Chicago infrastructure incident: multiple Kubernetes control plane VPS nodes became unreachable, causing the Deno Deploy Chicago cluster to temporarily lose quorum. Kubernetes quorum has been restored, but Vultr object storage in Chicago is still affected, so recovery is not complete and deno.com, deno.land, and Deno Deploy managed network traffic remain impacted.
- identified Jul 03, 2026, 12:53 AM UTC
We have identified the problem and are working on a fix. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues.
- resolved Jul 03, 2026, 03:00 AM UTC
The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.