Question
why ping too high?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×My location is in India, I am also facing the same problem. I have seen ping around 50 ms even for US based server, then what is the reason I am getting such a large ping?
NYC server
64 bytes from 104.236.230.153: icmpseq=0 ttl=50 time=359.753 ms
64 bytes from 104.236.230.153: icmpseq=1 ttl=50 time=282.658 ms
64 bytes from 104.236.230.153: icmpseq=2 ttl=50 time=508.879 ms
64 bytes from 104.236.230.153: icmpseq=3 ttl=50 time=238.196 ms
64 bytes from 104.236.230.153: icmpseq=4 ttl=50 time=238.225 ms
64 bytes from 104.236.230.153: icmpseq=5 ttl=50 time=236.841 ms
64 bytes from 104.236.230.153: icmpseq=6 ttl=50 time=492.605 ms
64 bytes from 104.236.230.153: icmpseq=7 ttl=50 time=469.729 ms
Request timeout for icmpseq 8
Request timeout for icmpseq 9
64 bytes from 104.236.230.153: icmpseq=10 ttl=50 time=475.159 ms
64 bytes from 104.236.230.153: icmpseq=11 ttl=50 time=394.934 ms
64 bytes from 104.236.230.153: icmpseq=12 ttl=50 time=317.286 ms
64 bytes from 104.236.230.153: icmpseq=13 ttl=50 time=544.458 ms
64 bytes from 104.236.230.153: icmpseq=14 ttl=50 time=456.275 ms
64 bytes from 104.236.230.153: icmpseq=15 ttl=50 time=375.436 ms
17 packets transmitted, 14 packets received, 17.6% packet loss
round-trip min/avg/max/stddev = 236.841/385.031/544.458/104.769 ms
Singapore server
4 bytes from 128.199.158.16: icmpseq=0 ttl=50 time=216.803 ms
Request timeout for icmpseq 1
64 bytes from 128.199.158.16: icmpseq=2 ttl=50 time=196.604 ms
64 bytes from 128.199.158.16: icmpseq=3 ttl=50 time=193.472 ms
64 bytes from 128.199.158.16: icmpseq=4 ttl=50 time=216.117 ms
64 bytes from 128.199.158.16: icmpseq=5 ttl=50 time=220.081 ms
64 bytes from 128.199.158.16: icmpseq=6 ttl=50 time=190.234 ms
64 bytes from 128.199.158.16: icmpseq=7 ttl=50 time=212.863 ms
64 bytes from 128.199.158.16: icmpseq=8 ttl=50 time=192.595 ms
64 bytes from 128.199.158.16: icmpseq=9 ttl=50 time=196.135 ms
64 bytes from 128.199.158.16: icmpseq=10 ttl=50 time=206.456 ms
64 bytes from 128.199.158.16: icmpseq=11 ttl=50 time=193.978 ms
64 bytes from 128.199.158.16: icmpseq=12 ttl=50 time=201.086 ms
64 bytes from 128.199.158.16: icmpseq=13 ttl=50 time=193.427 ms
64 bytes from 128.199.158.16: icmpseq=14 ttl=50 time=194.531 ms
64 bytes from 128.199.158.16: icmpseq=15 ttl=50 time=194.706 ms
64 bytes from 128.199.158.16: icmpseq=16 ttl=50 time=204.605 ms
Request timeout for icmpseq 17
64 bytes from 128.199.158.16: icmp_seq=18 ttl=50 time=194.145 ms
— 128.199.158.16 ping statistics —
19 packets transmitted, 17 packets received, 10.5% packet loss
round-trip min/avg/max/stddev = 190.234/201.049/220.081/9.540 ms
Date: June 27th, 2019
ISP: TechSavvy
My location: Guelph, Ontario, Canada
Server location: When creating a droplet I chose a location in Canada,,, IP returns Singapore…
This is a joke,,,
Pinging 165.22.250.185 with 32 bytes of data:
Reply from 165.22.250.185: bytes=32 time=361ms TTL=46
Reply from 165.22.250.185: bytes=32 time=372ms TTL=46
Reply from 165.22.250.185: bytes=32 time=289ms TTL=46
Reply from 165.22.250.185: bytes=32 time=438ms TTL=46
Thanks DigitalOcean