Resolved after 2 hours 53 minutes, on July 3, 2026.
The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact..
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 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..
- monitoring Jul 03, 2026, 12:53 AM UTC
The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues..
- 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..
Your product runs on more than Deno Deploy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services