What is the ideal ping value ?

mahadevan_iyer

mahadevan_iyer

Messages
84
Location
Kerala
ISP
BSNL Fiber
I did a ping and got this. Is this good ? I am getting around 20 - 25 Mbps as per my plan. Browsing is smooth. MTU is set at 1450. But I thing ping is high. WHat is the ideal ping for www.google.com

Code: 
PS C:\WINDOWS\system32> ping google.com

Pinging google.com [172.217.27.206] with 32 bytes of data:
Reply from 172.217.27.206: bytes=32 time=47ms TTL=116
Reply from 172.217.27.206: bytes=32 time=47ms TTL=116
Reply from 172.217.27.206: bytes=32 time=47ms TTL=116
Reply from 172.217.27.206: bytes=32 time=47ms TTL=116

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

Second time

Code: 
PS C:\WINDOWS\system32> ping www.google.com

Pinging www.google.com [216.58.214.4] with 32 bytes of data:
Reply from 216.58.214.4: bytes=32 time=333ms TTL=107
Reply from 216.58.214.4: bytes=32 time=333ms TTL=107
Reply from 216.58.214.4: bytes=32 time=333ms TTL=107
Reply from 216.58.214.4: bytes=32 time=333ms TTL=107

Ping statistics for 216.58.214.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 333ms, Maximum = 333ms, Average = 333ms
 
More pings

Code: 
PS C:\WINDOWS\system32> ping www.gamespot.com

Pinging cmg.cbsi.map.fastly.net [151.101.17.188] with 32 bytes of data:
Reply from 151.101.17.188: bytes=32 time=168ms TTL=56
Reply from 151.101.17.188: bytes=32 time=168ms TTL=56
Reply from 151.101.17.188: bytes=32 time=168ms TTL=56
Reply from 151.101.17.188: bytes=32 time=167ms TTL=56

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

RT.com

Code: 
PS C:\WINDOWS\system32> ping www.rt.com



Pinging wpc.en.rt.com [37.48.108.112] with 32 bytes of data:

Reply from 37.48.108.112: bytes=32 time=176ms TTL=54

Reply from 37.48.108.112: bytes=32 time=179ms TTL=54

Reply from 37.48.108.112: bytes=32 time=177ms TTL=54

Reply from 37.48.108.112: bytes=32 time=177ms TTL=54



Ping statistics for 37.48.108.112:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 176ms, Maximum = 179ms, Average = 177ms
 
It really depends on location and routing. If pings to your internet gateway is fine then there is no problem.
 
Tried pings using different DNS Servers Result below.

Using Cloudflare Malware DNS 1.1.1.2

Code: 
PS C:\WINDOWS\system32> ping google.com

Pinging google.com [216.58.196.174] with 32 bytes of data:
Reply from 216.58.196.174: bytes=32 time=19ms TTL=116
Reply from 216.58.196.174: bytes=32 time=19ms TTL=116
Reply from 216.58.196.174: bytes=32 time=19ms TTL=116
Reply from 216.58.196.174: bytes=32 time=19ms TTL=116

Ping statistics for 216.58.196.174:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 19ms, Average = 19ms
PS C:\WINDOWS\system32> ping www.yahoo.com

Pinging new-fp-shed.wg1.b.yahoo.com [202.165.107.50] with 32 bytes of data:
Reply from 202.165.107.50: bytes=32 time=223ms TTL=49
Reply from 202.165.107.50: bytes=32 time=223ms TTL=49
Reply from 202.165.107.50: bytes=32 time=224ms TTL=49
Reply from 202.165.107.50: bytes=32 time=224ms TTL=49

Ping statistics for 202.165.107.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 223ms, Maximum = 224ms, Average = 223ms
PS C:\WINDOWS\system32> ping www.polygon.com

Pinging vox-chorus.map.fastly.net [151.101.1.52] with 32 bytes of data:
Reply from 151.101.1.52: bytes=32 time=18ms TTL=55
Reply from 151.101.1.52: bytes=32 time=17ms TTL=55
Reply from 151.101.1.52: bytes=32 time=25ms TTL=55
Reply from 151.101.1.52: bytes=32 time=25ms TTL=55

Ping statistics for 151.101.1.52:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 25ms, Average = 21ms
PS C:\WINDOWS\system32> ping www.gamespot.com

Pinging cmg.cbsi.map.fastly.net [151.101.37.188] with 32 bytes of data:
Reply from 151.101.37.188: bytes=32 time=264ms TTL=54
Reply from 151.101.37.188: bytes=32 time=263ms TTL=54
Reply from 151.101.37.188: bytes=32 time=263ms TTL=54
Reply from 151.101.37.188: bytes=32 time=263ms TTL=54

Ping statistics for 151.101.37.188:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 263ms, Maximum = 264ms, Average = 263ms
PS C:\WINDOWS\system32> ping www.rt.com

Pinging wpc.en.rt.com [37.48.108.112] with 32 bytes of data:
Reply from 37.48.108.112: bytes=32 time=175ms TTL=48
Reply from 37.48.108.112: bytes=32 time=176ms TTL=48
Reply from 37.48.108.112: bytes=32 time=176ms TTL=48
Reply from 37.48.108.112: bytes=32 time=175ms TTL=48

Ping statistics for 37.48.108.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 175ms, Maximum = 176ms, Average = 175ms
PS C:\WINDOWS\system32> ping www.mi.com

Pinging xiaomiipv6.v.baishan-cloud.net [128.1.104.139] with 32 bytes of data:
Reply from 128.1.104.139: bytes=32 time=253ms TTL=52
Reply from 128.1.104.139: bytes=32 time=252ms TTL=52
Reply from 128.1.104.139: bytes=32 time=252ms TTL=52
Reply from 128.1.104.139: bytes=32 time=252ms TTL=52

Ping statistics for 128.1.104.139:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 252ms, Maximum = 253ms, Average = 252ms
PS C:\WINDOWS\system32> ping www.amazon.in

Pinging d1elgm1ww0d6wo.cloudfront.net [54.192.151.37] with 32 bytes of data:
Reply from 54.192.151.37: bytes=32 time=88ms TTL=240
Reply from 54.192.151.37: bytes=32 time=88ms TTL=240
Reply from 54.192.151.37: bytes=32 time=87ms TTL=240
Reply from 54.192.151.37: bytes=32 time=88ms TTL=240

Ping statistics for 54.192.151.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 87ms, Maximum = 88ms, Average = 87ms
PS C:\WINDOWS\system32> ping www.flipkart.com

Pinging flipkart.com [163.53.78.128] with 32 bytes of data:
Reply from 163.53.78.128: bytes=32 time=258ms TTL=54
Reply from 163.53.78.128: bytes=32 time=257ms TTL=54
Reply from 163.53.78.128: bytes=32 time=257ms TTL=54
Reply from 163.53.78.128: bytes=32 time=257ms TTL=54

Ping statistics for 163.53.78.128:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 257ms, Maximum = 258ms, Average = 257ms
PS C:\WINDOWS\system32>

Next DNS

Code: 
PS C:\WINDOWS\system32> ping www.google.com

Pinging www.google.com [172.217.27.196] with 32 bytes of data:
Reply from 172.217.27.196: bytes=32 time=43ms TTL=115
Reply from 172.217.27.196: bytes=32 time=42ms TTL=115
Reply from 172.217.27.196: bytes=32 time=42ms TTL=115
Reply from 172.217.27.196: bytes=32 time=43ms TTL=115

Ping statistics for 172.217.27.196:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 43ms, Average = 42ms
PS C:\WINDOWS\system32> ping www.yahoo.com

Pinging new-fp-shed.wg1.b.yahoo.com [202.165.107.50] with 32 bytes of data:
Reply from 202.165.107.50: bytes=32 time=122ms TTL=44
Reply from 202.165.107.50: bytes=32 time=123ms TTL=44
Reply from 202.165.107.50: bytes=32 time=123ms TTL=44
Reply from 202.165.107.50: bytes=32 time=123ms TTL=44

Ping statistics for 202.165.107.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 123ms, Average = 122ms
PS C:\WINDOWS\system32> ping www.polygon.com

Pinging vox-chorus.map.fastly.net [151.101.13.52] with 32 bytes of data:
Reply from 151.101.13.52: bytes=32 time=280ms TTL=53
Reply from 151.101.13.52: bytes=32 time=293ms TTL=53
Reply from 151.101.13.52: bytes=32 time=278ms TTL=53
Reply from 151.101.13.52: bytes=32 time=278ms TTL=53

Ping statistics for 151.101.13.52:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 278ms, Maximum = 293ms, Average = 282ms
PS C:\WINDOWS\system32> ping www.gamespot.com

Pinging cmg.cbsi.map.fastly.net [151.101.17.188] with 32 bytes of data:
Reply from 151.101.17.188: bytes=32 time=178ms TTL=56
Reply from 151.101.17.188: bytes=32 time=178ms TTL=56
Reply from 151.101.17.188: bytes=32 time=178ms TTL=56
Reply from 151.101.17.188: bytes=32 time=178ms TTL=56

Ping statistics for 151.101.17.188:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 178ms, Maximum = 178ms, Average = 178ms
PS C:\WINDOWS\system32> ping www.rt.com

Pinging wpc.en.rt.com [37.48.108.112] with 32 bytes of data:
Reply from 37.48.108.112: bytes=32 time=174ms TTL=54
Reply from 37.48.108.112: bytes=32 time=175ms TTL=54
Reply from 37.48.108.112: bytes=32 time=175ms TTL=54
Reply from 37.48.108.112: bytes=32 time=174ms TTL=54

Ping statistics for 37.48.108.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 174ms, Maximum = 175ms, Average = 174ms
PS C:\WINDOWS\system32> ping www.mi.com

Pinging xiaomiipv6.v.baishan-cloud.net [128.1.104.139] with 32 bytes of data:
Reply from 128.1.104.139: bytes=32 time=28ms TTL=54
Reply from 128.1.104.139: bytes=32 time=28ms TTL=54
Reply from 128.1.104.139: bytes=32 time=28ms TTL=54
Reply from 128.1.104.139: bytes=32 time=27ms TTL=54

Ping statistics for 128.1.104.139:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 28ms, Average = 27ms
PS C:\WINDOWS\system32> ping www.amazon.in

Pinging e15322.e22.akamaiedge.net [184.29.25.49] with 32 bytes of data:
Reply from 184.29.25.49: bytes=32 time=83ms TTL=55
Reply from 184.29.25.49: bytes=32 time=83ms TTL=55
Reply from 184.29.25.49: bytes=32 time=84ms TTL=55
Reply from 184.29.25.49: bytes=32 time=83ms TTL=55

Ping statistics for 184.29.25.49:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 84ms, Average = 83ms
PS C:\WINDOWS\system32> ping www.flipkart.com

Pinging flipkart.com [163.53.78.128] with 32 bytes of data:
Reply from 163.53.78.128: bytes=32 time=24ms TTL=56
Reply from 163.53.78.128: bytes=32 time=24ms TTL=56
Reply from 163.53.78.128: bytes=32 time=23ms TTL=56
Reply from 163.53.78.128: bytes=32 time=24ms TTL=56

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

For me NEXT DNS seems better.
 
Better? Isn't that just margin of error.
I don't know what IP you're getting for google.com, a quick search tells it's located in Mumbai & Chennai respectively.

I use 1.1.1.1 and for google.com I get maa05s05-in-f14.1e100.net (172.217.163.174)

Code: 
PING google.com (172.217.163.174) 56(84) bytes of data.
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=1 ttl=117 time=55.7 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=2 ttl=117 time=56.1 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=3 ttl=117 time=55.4 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=4 ttl=117 time=56.1 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=5 ttl=117 time=55.5 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=6 ttl=117 time=55.3 ms
^C
--- google.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 55.330/55.713/56.158/0.404 ms

No idea what's up with it on your side :(
 
You must log in or register to reply here.

Similar threads

theOne235
What is the ideal MTU for Tata Play Fiber?
Replies
2
Views
814
albonycal
albonycal
H
What is the average ping in vidharba side?
Replies
0
Views
600
Hamad
H
5trange
Very high ping to Steam(Valve) India servers
2 3 4
Replies
34
Views
10,387
talk2g
talk2g
JB701
Is Excitel blocking PPTP VPN and ping/ICMP
Replies
5
Views
3,103
philip marlowe
philip marlowe
Back