Nope. Same problem today. Yet, the addresses resolve just fine.
pi@compute:~/build$ ping ports.ubuntu.com
PING ports.ubuntu.com(aerodent.canonical.com (2620:2d:4000:1::19)) 56 data bytes
64 bytes from aerodent.canonical.com (2620:2d:4000:1::19): icmp_seq=1 ttl=52 time=94.9 ms
64 bytes from aerodent.canonical.com (2620:2d:4000:1::19): icmp_seq=2 ttl=52 time=94.9 ms
64 bytes from aerodent.canonical.com (2620:2d:4000:1::19): icmp_seq=3 ttl=52 time=94.9 ms
64 bytes from aerodent.canonical.com (2620:2d:4000:1::19): icmp_seq=4 ttl=52 time=93.9 ms
^C
--- ports.ubuntu.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4004ms
rtt min/avg/max/mdev = 93.915/94.648/94.924/0.424 ms
pi@compute:~/build$ ping apt.arbian.com
PING apt.arbian.com (205.144.171.183) 56(84) bytes of data.
64 bytes from 205-144-171-183.alchemy.net (205.144.171.183): icmp_seq=1 ttl=110 time=62.9 ms
64 bytes from 205-144-171-183.alchemy.net (205.144.171.183): icmp_seq=2 ttl=110 time=63.5 ms
64 bytes from 205-144-171-183.alchemy.net (205.144.171.183): icmp_seq=3 ttl=110 time=63.0 ms
64 bytes from 205-144-171-183.alchemy.net (205.144.171.183): icmp_seq=4 ttl=110 time=63.0 ms