Gaming and Pings

[syntaX1]

My question is; why are our pings so terrible when it comes to international sites/servers?

I can browse google.com, but what happens when I try to ping it...

----------------------------------------------------------------

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

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.239.51.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

----------------------------------------------------------------

Would changing the MTU help this? Would smaller packets help reduce the ping times? I've tried, but doesn't seem to help much. Has anyone had any success in achieving low international pings?

 

[DarkSkies]

Weird I can ping them fine. Might be the router of firewall blocking the ping attempts?

--------------------------------------------------------------
Pinging google.com [216.239.53.100] with 32 bytes of data:

Reply from 216.239.53.100: bytes=32 time=543ms TTL=46
Reply from 216.239.53.100: bytes=32 time=629ms TTL=46
Reply from 216.239.53.100: bytes=32 time=774ms TTL=46
Reply from 216.239.53.100: bytes=32 time=672ms TTL=46

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

 

[syntaX1]

Odd, I've reinstalled to start with a fresh installation, so no firewall up at the moment and I'm dialing out through through the router.

M-Web perhaps?

I wonder if there is a way to achieve better pings.

 

[val]

Pinging www.google.com [216.239.57.99] with 32 bytes of

Reply from 216.239.57.99: bytes=32 time=313ms TTL=42
Reply from 216.239.57.99: bytes=32 time=297ms TTL=42
Reply from 216.239.57.99: bytes=32 time=297ms TTL=42
Reply from 216.239.57.99: bytes=32 time=297ms TTL=42

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

 

[syntaX1]

----------------------------------------------------------------
Pinging www.google.com [216.239.39.99] with 32 bytes of data:

Request timed out.
Reply from 216.239.39.99: bytes=32 time=421ms TTL=49
Reply from 216.239.39.99: bytes=32 time=615ms TTL=49
Reply from 216.239.39.99: bytes=32 time=587ms TTL=49

Ping statistics for 216.239.39.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 421ms, Maximum = 615ms, Average = 541ms
----------------------------------------------------------------

Better than before, but still not what I expect from 'Super Fast Internet'.

 

[val]

Pinging www.google.com [216.239.37.99] with 32 bytes of data:

Reply from 216.239.37.99: bytes=32 time=270ms TTL=48
Reply from 216.239.37.99: bytes=32 time=261ms TTL=48
Reply from 216.239.37.99: bytes=32 time=260ms TTL=48
Reply from 216.239.37.99: bytes=32 time=261ms TTL=48

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