Pings to International Servers

Hi

Would anybody mind pinging the following servers and posting the average ping times. I am just curious to know if there is any difference in ISPs regarding pings to international servers.

I'm on MWeb Standard 6Meg uncapped.

UK
www.bbc.co.uk = 201ms
www.amazon.co.uk = 208ms

US
www.cbs.com = 320ms
www.amazon.com = 303ms

AUS
www.abc.net.au = 482ms

Thanks

Difference is not only ISP but also location. Cape Town tends to have lower international pings.

I'm on OpenWeb 20Mbit uncapped.

bbc.co.uk = 158ms
amazon.co.uk = rejecting ICMP pings (165ms with TCP traceroute)

cbs.com = 284ms
amazon.com = rejecting ICMP pings (231ms with TCP traceroute)

www.abc.net.au = redirecting to a local address
abc.net.au = rejecting ICMP pings (443ms with TCP traceroute)
 
Last edited:
Ping output:
PING www.bbc.net.uk (212.58.244.71): 56 data bytes
64 bytes from 212.58.244.71: icmp_seq=0 ttl=51 time=191.113 ms
64 bytes from 212.58.244.71: icmp_seq=1 ttl=51 time=191.448 ms
64 bytes from 212.58.244.71: icmp_seq=2 ttl=51 time=190.262 ms
64 bytes from 212.58.244.71: icmp_seq=3 ttl=51 time=189.854 ms

--- www.bbc.net.uk ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 189.854/190.669/191.448/0.639 ms

Ping output:
PING www.cbs.com (64.30.228.50): 56 data bytes
64 bytes from 64.30.228.50: icmp_seq=0 ttl=230 time=312.981 ms
64 bytes from 64.30.228.50: icmp_seq=1 ttl=230 time=313.181 ms
64 bytes from 64.30.228.50: icmp_seq=2 ttl=230 time=313.254 ms
64 bytes from 64.30.228.50: icmp_seq=3 ttl=230 time=313.822 ms

--- www.cbs.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 312.981/313.310/313.822/0.312 ms


Anything past LEVEL3.NET is a "hit_or_miss" (Amsterdam)
 
Thought I'd compare my OW Uncapped and AH capped accounts quickly:

bbc.co.uk

OW
Code:
PING bbc.co.uk (212.58.244.20) from 196.209.216.xxx: 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=51 time=155.556 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=51 time=155.996 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=51 time=155.613 ms

--- bbc.co.uk ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 155.556/155.722/155.996/0.195 ms

AH
Code:
PING 212.58.244.20 (212.58.244.20) from 105.237.49.xxx: 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=53 time=155.673 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=53 time=153.775 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=53 time=152.722 ms

--- 212.58.244.20 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 152.722/154.057/155.673/1.221 ms

www.cbs.com

OW
Code:
PING www.cbs.com (64.30.228.49) from 196.209.216.xxx: 56 data bytes
64 bytes from 64.30.228.49: icmp_seq=0 ttl=232 time=284.066 ms
64 bytes from 64.30.228.49: icmp_seq=1 ttl=232 time=284.136 ms
64 bytes from 64.30.228.49: icmp_seq=2 ttl=232 time=283.847 ms

--- www.cbs.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 283.847/284.016/284.136/0.123 ms

AH
Code:
PING 64.30.228.49 (64.30.228.49) from 105.237.49.xxx: 56 data bytes
64 bytes from 64.30.228.49: icmp_seq=0 ttl=236 time=281.057 ms
64 bytes from 64.30.228.49: icmp_seq=1 ttl=236 time=281.020 ms
64 bytes from 64.30.228.49: icmp_seq=2 ttl=236 time=281.305 ms

--- 64.30.228.49 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 281.020/281.127/281.305/0.127 ms

www.uq.edu.au

OW
Code:
PING www.uq.edu.au (130.102.131.70) from 196.209.216.xxx: 56 data bytes
64 bytes from 130.102.131.70: icmp_seq=0 ttl=105 time=457.521 ms
64 bytes from 130.102.131.70: icmp_seq=1 ttl=105 time=446.581 ms
64 bytes from 130.102.131.70: icmp_seq=2 ttl=105 time=455.170 ms

--- www.uq.edu.au ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 446.581/453.091/457.521/4.702 ms

AH
Code:
PING www.uq.edu.au (130.102.131.70) from 105.237.49.xxx: 56 data bytes
64 bytes from 130.102.131.70: icmp_seq=0 ttl=100 time=462.797 ms
64 bytes from 130.102.131.70: icmp_seq=1 ttl=100 time=462.035 ms
64 bytes from 130.102.131.70: icmp_seq=2 ttl=100 time=463.048 ms

--- www.uq.edu.au ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 462.035/462.627/463.048/0.431 ms

To be honest I'm surprised by these results. My IS accounts always used to give better latency than the MTN accounts. AH must have tweaked something.
 
Telkom uncapped from PMB:
Code:
Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=250ms TTL=50
Reply from 212.58.244.20: bytes=32 time=241ms TTL=50
Reply from 212.58.244.20: bytes=32 time=264ms TTL=50
Reply from 212.58.244.20: bytes=32 time=242ms TTL=50
Pretty horrible at the moment. Ping is usually between 197 and 210.

I've found that Afrihost seems to have the best ping because of MTN's fibre backbone, which cuts out a huge portion of the delay.
 
Thanks to everyone.

Looking at the stats, it looks like the Cape guys get a good 30ms less on average than up here in Joburg. Lucky bums!
 
Telkom uncapped from PMB:
Code:
Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=250ms TTL=50
Reply from 212.58.244.20: bytes=32 time=241ms TTL=50
Reply from 212.58.244.20: bytes=32 time=264ms TTL=50
Reply from 212.58.244.20: bytes=32 time=242ms TTL=50
Pretty horrible at the moment. Ping is usually between 197 and 210.

I've found that Afrihost seems to have the best ping because of MTN's fibre backbone, which cuts out a huge portion of the delay.

Ping is fine here on TI:
Pinging bbc.co.uk [212.58.246.103] with 32 bytes of data:
Reply from 212.58.246.103: bytes=32 time=168ms TTL=50
Reply from 212.58.246.103: bytes=32 time=168ms TTL=50
Reply from 212.58.246.103: bytes=32 time=168ms TTL=50
Reply from 212.58.246.103: bytes=32 time=169ms TTL=50
 
I'm on Afrihost Capped Account 10mb line


www.bbc.co.uk = 153ms
www.amazon.co.uk = dead


www.cbs.com = 281ms
www.amazon.com = dead


www.abc.net.au = 8ms

I have had sites that have been inaccessible whenever I use my 4mb capped Afrihost account. Sites such as the steam store, Facebook, Amazon and a few others would simply not resolve.

I found that using the Google DNS servers (8.8.8.8, 8.8.4.4) made the sites accessible again. Not sure what is at play with the Afrihost DNS servers.
 
Top
Sign up to the MyBroadband newsletter
X