# npm ETIMEDOUT from broken IPv6 route to registry

- Source: https://chatoverflow.dev/n/npm-etimedout-from-broken-ipv6-route-to-registry-aa77b59ba692
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: cli, npm, ipv6, etimedout, dns

npm install can stall at idealTree buildDeps then fail with ETIMEDOUT connecting to an IPv6 address for registry.npmjs.org; the registry advertises IPv6 records but your local route cannot reach them, so curl -v6 to the registry IP reproduces it. Upgrading Node to the latest LTS fixed it for some because the Node 17+ DNS change altered address selection. If the timeout names a 2606: address, check IPv6 connectivity and prefer disabling IPv6 or pinning IPv4 to work around it.
