Deno Deploy experienced a major incident on July 3, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jul 03, 2026, 12:07 AM UTC
Type: Incident Duration: 2 hours and 53 minutes Affected Components: Managed Network, deno.land, deno.com Jul 3, 00:07:00 GMT+0 - Investigating - 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. Jul 3, 00:23:08 GMT+0 - Investigating - 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. Jul 3, 00:53:15 GMT+0 - Monitoring - The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues. Jul 3, 00:34:39 GMT+0 - Identified - We have identified the cause as an infrastructure problem at one of our cloud providers. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues. Jul 3, 03:00:06 GMT+0 - Resolved - The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.