3 ms·
They also seem to have fixed the routing issues in Europe: $ ping -n -c 4 speedtest-ams1.digitalocean.com PING speedtest-ams1.digitalocean.com (198.21
by spindritf 13y ago
They also seem to have fixed the routing issues in Europe:
$ ping -n -c 4 speedtest-ams1.digitalocean.com
PING speedtest-ams1.digitalocean.com (198.211.119.108) 56(84) bytes of data.
64 bytes from 198.211.119.108: icmp_req=1 ttl=55 time=35.2 ms
64 bytes from 198.211.119.108: icmp_req=2 ttl=55 time=36.2 ms
64 bytes from 198.211.119.108: icmp_req=3 ttl=55 time=35.1 ms
64 bytes from 198.211.119.108: icmp_req=4 ttl=55 time=33.8 ms
--- speedtest-ams1.digitalocean.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 33.854/35.095/36.208/0.845 ms
It used to be over 100ms, almost as much as to NYC2.
- osiemens 13y agoAccording to Digitalocean the routing issue wasn't on their side. From what I could see, the cause of the latency was asymmetric routing. Some of my Amsterdam -> Amsterdam traffic had its return traffic sent via NY. This was resolved when they got more bandwidth and were able to disconnect Cogent some time last week.