Question

why ping too high?

  • Posted January 27, 2014

tested all servers. http://speedtest-sfo1.digitalocean.com/ http://speedtest-ams2.digitalocean.com/ http://speedtest-ams1.digitalocean.com/ http://speedtest-nyc2.digitalocean.com/ http://speedtest-ny1.digitalocean.com/

for test my line quality result for google.com.my lower.

RESULT :

Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\post>ping speedtest-ny1.digitalocean.com

Pinging speedtest-ny1.digitalocean.com [198.211.112.36] with 32 bytes of data:

Reply from 198.211.112.36: bytes=32 time=294ms TTL=52 Reply from 198.211.112.36: bytes=32 time=292ms TTL=52 Reply from 198.211.112.36: bytes=32 time=299ms TTL=52 Reply from 198.211.112.36: bytes=32 time=293ms TTL=52

Ping statistics for 198.211.112.36: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 292ms, Maximum = 299ms, Average = 294ms

C:\Documents and Settings\post>ping speedtest-nyc2.digitalocean.com

Pinging speedtest-nyc2.digitalocean.com [162.243.123.82] with 32 bytes of data:

Reply from 162.243.123.82: bytes=32 time=293ms TTL=52 Reply from 162.243.123.82: bytes=32 time=315ms TTL=52 Reply from 162.243.123.82: bytes=32 time=298ms TTL=52 Reply from 162.243.123.82: bytes=32 time=300ms TTL=52

Ping statistics for 162.243.123.82: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 293ms, Maximum = 315ms, Average = 301ms

C:\Documents and Settings\post>ping speedtest-ams1.digitalocean.com

Pinging speedtest-ams1.digitalocean.com [146.185.183.239] with 32 bytes of data:

Reply from 146.185.183.239: bytes=32 time=309ms TTL=48 Reply from 146.185.183.239: bytes=32 time=294ms TTL=48 Reply from 146.185.183.239: bytes=32 time=302ms TTL=48 Reply from 146.185.183.239: bytes=32 time=288ms TTL=48

Ping statistics for 146.185.183.239: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 288ms, Maximum = 309ms, Average = 298ms

C:\Documents and Settings\post>ping speedtest-ams2.digitalocean.com

Pinging speedtest-ams2.digitalocean.com [95.85.7.154] with 32 bytes of data:

Reply from 95.85.7.154: bytes=32 time=359ms TTL=46 Reply from 95.85.7.154: bytes=32 time=359ms TTL=46 Reply from 95.85.7.154: bytes=32 time=358ms TTL=46 Reply from 95.85.7.154: bytes=32 time=360ms TTL=46

Ping statistics for 95.85.7.154: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 358ms, Maximum = 360ms, Average = 359ms

C:\Documents and Settings\post>ping speedtest-sfo1.digitalocean.com

Pinging speedtest-sfo1.digitalocean.com [162.243.146.51] with 32 bytes of data:

Reply from 162.243.146.51: bytes=32 time=289ms TTL=51 Reply from 162.243.146.51: bytes=32 time=283ms TTL=51 Reply from 162.243.146.51: bytes=32 time=291ms TTL=51 Reply from 162.243.146.51: bytes=32 time=293ms TTL=51

Ping statistics for 162.243.146.51: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 283ms, Maximum = 293ms, Average = 289ms

C:\Documents and Settings\post>ping google.com.my

Pinging google.com.my [74.125.135.94] with 32 bytes of data:

Reply from 74.125.135.94: bytes=32 time=60ms TTL=52 Reply from 74.125.135.94: bytes=32 time=27ms TTL=52 Reply from 74.125.135.94: bytes=32 time=27ms TTL=52 Reply from 74.125.135.94: bytes=32 time=27ms TTL=52

Ping statistics for 74.125.135.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 60ms, Average = 35ms

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

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

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: icmp_seq=0 ttl=50 time=359.753 ms 64 bytes from 104.236.230.153: icmp_seq=1 ttl=50 time=282.658 ms 64 bytes from 104.236.230.153: icmp_seq=2 ttl=50 time=508.879 ms 64 bytes from 104.236.230.153: icmp_seq=3 ttl=50 time=238.196 ms 64 bytes from 104.236.230.153: icmp_seq=4 ttl=50 time=238.225 ms 64 bytes from 104.236.230.153: icmp_seq=5 ttl=50 time=236.841 ms 64 bytes from 104.236.230.153: icmp_seq=6 ttl=50 time=492.605 ms 64 bytes from 104.236.230.153: icmp_seq=7 ttl=50 time=469.729 ms Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 64 bytes from 104.236.230.153: icmp_seq=10 ttl=50 time=475.159 ms 64 bytes from 104.236.230.153: icmp_seq=11 ttl=50 time=394.934 ms 64 bytes from 104.236.230.153: icmp_seq=12 ttl=50 time=317.286 ms 64 bytes from 104.236.230.153: icmp_seq=13 ttl=50 time=544.458 ms 64 bytes from 104.236.230.153: icmp_seq=14 ttl=50 time=456.275 ms 64 bytes from 104.236.230.153: icmp_seq=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: icmp_seq=0 ttl=50 time=216.803 ms Request timeout for icmp_seq 1 64 bytes from 128.199.158.16: icmp_seq=2 ttl=50 time=196.604 ms 64 bytes from 128.199.158.16: icmp_seq=3 ttl=50 time=193.472 ms 64 bytes from 128.199.158.16: icmp_seq=4 ttl=50 time=216.117 ms 64 bytes from 128.199.158.16: icmp_seq=5 ttl=50 time=220.081 ms 64 bytes from 128.199.158.16: icmp_seq=6 ttl=50 time=190.234 ms 64 bytes from 128.199.158.16: icmp_seq=7 ttl=50 time=212.863 ms 64 bytes from 128.199.158.16: icmp_seq=8 ttl=50 time=192.595 ms 64 bytes from 128.199.158.16: icmp_seq=9 ttl=50 time=196.135 ms 64 bytes from 128.199.158.16: icmp_seq=10 ttl=50 time=206.456 ms 64 bytes from 128.199.158.16: icmp_seq=11 ttl=50 time=193.978 ms 64 bytes from 128.199.158.16: icmp_seq=12 ttl=50 time=201.086 ms 64 bytes from 128.199.158.16: icmp_seq=13 ttl=50 time=193.427 ms 64 bytes from 128.199.158.16: icmp_seq=14 ttl=50 time=194.531 ms 64 bytes from 128.199.158.16: icmp_seq=15 ttl=50 time=194.706 ms 64 bytes from 128.199.158.16: icmp_seq=16 ttl=50 time=204.605 ms Request timeout for icmp_seq 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

now allready february. <br>why still doesnt have singapore DC? <br>please reply.

Our guess would be that you are somewhere in Indonesia which explains the high ping times as the larger the geographic distance is between the two end points the more latency you will have. <br> <br>The good news is that we are neck deep in rolling out our Singapore region which will be launching in February and that should provide significantly better ping times for you. <br> <br>Thanks!

Where are you located geographically?