download.proxmox.com unreachable from Colombia (EHOSTUNREACH on na2.cdn node)

[cirivas]

Hi,

Since 2026-08-12 ~07:14 (local time, UTC-5) the Proxmox apt repositories
(http://download.proxmox.com/debian/{pve,pbs,pbs-client}, bookworm) intermittently
fail with "connect (113: No route to host)" from my host in Colombia (ISP ETB).

DNS chain:
download.proxmox.com
-> CNAME download.cdn.proxmox.com
-> CNAME co.sa.cdn.proxmox.com
-> na2.cdn.proxmox.com -> 95.133.229.241 (UNREACHABLE)
-> na.cdn.proxmox.com -> 66.70.154.82 (OK, HTTP 200)

Tested resolvers (200.21.200.10, 1.1.1.1, 8.8.8.8, 9.9.9.9, 208.67.222.222,
208.67.220.220, 64.6.64.6, 8.8.4.4): the authoritative server rotates between
na.cdn (66.70.154.82) and na2.cdn (95.133.229.241) on a round-robin basis,
so failures are intermittent depending on which node is served.

Diagnostics against 95.133.229.241:80:
- curl --resolve download.proxmox.com:80:95.133.229.241 : FAIL 5/5 (no headers)
- traceroute: packets die inside Arelion backbone (62.115.x / 67.210.x),
never reach the destination -> route blackholed / peering issue.
- whois 95.133.229.241: servinga GmbH (DE-SERVINGA-20090123).
- No proxy, UFW policies ACCEPT, local firewall not the cause.
- Same host reaches na.cdn (66.70.154.82), de.cdn (212.224.123.70) and
fr.cdn (51.91.38.34) fine (HTTP 200).

Please check the na2.cdn.proxmox.com node / the Arelion routing towards
95.133.229.241 from Colombia/LatAm.

Best regards,

 

[Stoiko Ivanov]

Thanks for the report - there was an outage on that system - but it should be reachable again.
We'll take a look.

In the meantime - you could point your system to `na.cdn.proxmox.com` (by making an entry in /etc/hosts for download.proxmox.com to the ip-address of na.cdn.proxmox.com) - but do remove the entry after a while - our cdn mirrors are not guaranteed to keep their IP-addresses.

I hope this helps!

 

[Stoiko Ivanov]

For completeness sake : na2.cdn.proxmox.com has been live and in service again for a while now.