Deno - Deno Deploy Chicago cluster outage – Incident details

All systems operational

Show current status

Deno Deploy Chicago cluster outage

ResolvedMajor outage2 hours 53 minutes

Affected

Deno Deploy

Partial outage from 12:07 AM to 12:23 AM, Major outage from 12:23 AM to 12:53 AM, Operational from 12:53 AM to 3:00 AM

Managed Network

Partial outage from 12:07 AM to 12:23 AM, Major outage from 12:23 AM to 12:53 AM, Operational from 12:53 AM to 3:00 AM

Websites

Partial outage from 12:07 AM to 12:23 AM, Major outage from 12:23 AM to 12:53 AM, Operational from 12:53 AM to 3:00 AM

deno.land

Partial outage from 12:07 AM to 12:23 AM, Major outage from 12:23 AM to 12:53 AM, Operational from 12:53 AM to 3:00 AM

deno.com

Partial outage from 12:07 AM to 12:23 AM, Major outage from 12:23 AM to 12:53 AM, Operational from 12:53 AM to 3:00 AM

  • ResolvedUTC
    The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.
  • MonitoringUTC
    The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues.
  • IdentifiedUTC
    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.
  • UpdateUTC
    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.
  • InvestigatingUTC
    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.