3 ms·
PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=2.099 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=2.073 ms 64 bytes
by wakokueh 9y ago
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=2.099 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=2.073 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=1.963 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=2.089 ms
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=60 time=1.908 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=1.888 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=1.993 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=1.891 ms
From SG too. Could it be... just you?
- isatty 9y agoJust him. Starhub Fiber: ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=3.111 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=3.172 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=3.301 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=3.018 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=3.218 ms ^C --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 3.018/3.164/3.301/0.096 ms fwiw Google DNS is around the same, 2.942ms average.
- sho 9y agoInteresting, mine is bad too. From singtel: Host Loss% Snt Last Avg Best Wrst StDev 1. 192.168.1.254 0.0% 75 1.3 1.6 1.1 14.8 1.6 2. bbXXX-XXX-XXX-XX.singnet.com.sg 0.0% 75 3.4 2.8 1.9 18.7 2.5 3. 202.166.123.134 0.0% 75 3.2 3.5 2.7 15.9 2.0 4. 202.166.123.133 0.0% 75 3.0 3.0 2.4 6.6 0.7 5. ae8-0.tp-cr03.singnet.com.sg 0.0% 75 3.1 3.3 2.8 6.9 0.7 6. ae4-0.tp-er03.singnet.com.sg 0.0% 75 2.9 3.1 2.6 6.7 0.5 7. 203.208.191.197 0.0% 75 7.8 4.6 2.9 18.3 3.6 8. 203.208.149.138 0.0% 75 3.0 7.5 2.7 67.2 13.4 9. 203.208.153.126 0.0% 75 182.8 186.9 174.4 327.7 20.5 203.208.172.226 203.208.172.178 203.208.158.50 203.208.152.214 203.208.173.106 203.208.149.58 203.208.149.30 10. ix-xe-0-1-2-0.tcore2.pdi-palo-alto.as6453.net 0.0% 74 201.4 190.5 183.9 210.1 5.9 11. if-ae-5-2.tcore2.sqn-san-jose.as6453.net 0.0% 74 181.4 184.7 179.4 197.9 4.6 12. if-ae-1-2.tcore1.sqn-san-jose.as6453.net 0.0% 74 177.8 177.3 172.0 190.0 4.8 13. 63.243.205.106 0.0% 74 179.2 184.2 179.1 196.2 4.5 14. 1dot1dot1dot1.cloudflare-dns.com 0.0% 74 191.9 184.7 172.4 202.3 6.6 Looks like singtel has some bad routing rules for Cloudflare and it's going through to the USA rather than hitting a local PoP. Might send CloudFlare a quick email as they'll probably want singtel to correct this.
- ValentineC 9y agoM1 Business: PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=3.57 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=3.30 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=3.31 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=3.21 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=3.21 ms PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=3.15 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=3.17 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=2.34 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=2.93 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=3.19 ms MyRepublic: PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=1.88 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=1.93 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=1.96 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=1.85 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=1.85 ms PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=1.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=1.66 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=1.40 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=1.38 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=59 time=1.60 ms Looks like Google DNS's still a little bit faster.