# Deno Deploy: Deno Deploy Chicago cluster outage

- Impact (vendor’s label): unknown
- Status: monitoring
- Started: 2026-07-01 16:25 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 3 · Affected components: deno.com, deno.land, Managed Network
- [Vendor status page: https://denostatus.com/incident/cmr2b5mjh00xa0kpyhdeblv3y](https://denostatus.com/incident/cmr2b5mjh00xa0kpyhdeblv3y)
- [Company: Deno Deploy](https://rewindex.com/company/deno-deploy.md)

## Timeline of updates

- **investigating** 2026-07-01 16:25 UTC: Starting around 09:25 PDT, the Deno Deploy Chicago cluster experienced an outage. This affected 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 were affected as well. The Deno Deploy console remained available, but builds triggered via GitHub integration, CLI, or API were failing because builds run in Chicago. Sandbox creation in Chicago was also failing..
- **monitoring** 2026-07-01 17:15 UTC: The Chicago cluster outage was resolved around 10:15 PDT and affected services have recovered. We are continuing to monitor..
- **resolved** 2026-07-01 17:15 UTC: This incident has been resolved..


---
Canonical: https://rewindex.com/company/deno-deploy/incidents/cmr2b5mjh00xa0kpyhdeblv3y · Markdown: https://rewindex.com/company/deno-deploy/incidents/cmr2b5mjh00xa0kpyhdeblv3y.md · JSON: https://rewindex.com/api/v1/companies/deno-deploy/incidents/cmr2b5mjh00xa0kpyhdeblv3y · Generated 2026-10-20T00:14:29.549Z