For me, Japan is bad -> 27.120.102.123 -> 290-300ms ping

Test IP: 206.123.122.2

Opening the file >>/var/www/pinginfo/testprint() on closed filehandle MYFILE at /root/perlscripts/pingm.pl line 123.

Hey guys, Sam here from anyNode.net to offer you guys some discounts on our standard VPS packages. Our current VPS offerings are OpenVZ 2.6.32 based. All of our plans include vSwap and are capable of

Test IP: 206.123.122.2

RX bytes:126672 (123.7 KiB) TX bytes:113335 (110.6 KiB)

* On the node or in the privileged VM, use iptables to restrict traffic on port 123 to those timeservers.

10. vac1-1-n7.fr.eu.firewall 0.0% 5 123.0 126.3 121.7 129.6 3.7

cup:~ mobile$ ping.cdn.jsdelivr.netPING 531151672.r.worldcdn.net (109.123.117.122): 56 data bytes64 bytes from 109.123.117.122: icmp_seq=0 ttl=52 time=85.576 ms64 bytes from 109.123.117.122: icmp_seq=

London, United Kingdom (gblon01): Okay 1.2 1.6 2.1 109.123.117.122

PING 531151672.r.worldcdn.net (109.123.117.122): 56 data bytes

Norfolk, England.

Hum @rm_, I also had that same problem, and exactly 123 seconds... Was either the same provider, a big coincidence or some other error that makes the clock jump 123 seconds. In my case the message was

With ntpdate sadly you can get hit by this:

6 ae-32-52.ebr2.Miami1.Level3.net (4.69.138.123) 5.302 ms 5.048 ms 4.974 ms

64 bytes from 72.29.87.105: icmp_req=2 ttl=49 time=123 ms

Hey guys, Sam here from anyNode.net to offer you guys some discounts on our standard VPS packages. Our current VPS offerings are OpenVZ 2.6.32 based. All of our plans include vSwap and are capable of

27 vac1-0-a9.fr.eu.vaccum (178.33.100.151) 10.824 ms 11.123 ms 12.009 ms

26 91.121.131.255 (91.121.131.255) 0.995 ms rbx-s6-6k.fr.eu (91.121.131.93) 1.123 ms 0.964 ms

(Quote)