hi,

those do look like ADSL pings to me Zyborg.

pings here from 3 customer locations on three different Fixed Wireless networks :-

Tatenhill - Staffs

PING 212.58.241.131 (212.58.241.131) 56(84) bytes of data.
64 bytes from 212.58.241.131: icmp_req=1 ttl=246 time=7.17 ms
64 bytes from 212.58.241.131: icmp_req=2 ttl=246 time=6.94 ms
64 bytes from 212.58.241.131: icmp_req=3 ttl=246 time=7.02 ms
64 bytes from 212.58.241.131: icmp_req=4 ttl=246 time=7.21 ms
64 bytes from 212.58.241.131: icmp_req=5 ttl=246 time=6.95 ms
64 bytes from 212.58.241.131: icmp_req=6 ttl=246 time=7.01 ms
64 bytes from 212.58.241.131: icmp_req=7 ttl=246 time=7.01 ms
64 bytes from 212.58.241.131: icmp_req=8 ttl=246 time=7.01 ms


West Sussex (East):-

PING 212.58.241.131 (212.58.241.131) 56(84) bytes of data.
64 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=4.54 ms
64 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=4.19 ms
64 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=4.18 ms
64 bytes from 212.58.241.131: icmp_seq=4 ttl=247 time=4.25 ms
64 bytes from 212.58.241.131: icmp_seq=5 ttl=247 time=4.38 ms
64 bytes from 212.58.241.131: icmp_seq=6 ttl=247 time=4.31 ms

West Sussex (West)

PING 212.58.241.131 (212.58.241.131) 56(84) bytes of data.
64 bytes from 212.58.241.131: icmp_seq=1 ttl=246 time=7.56 ms
64 bytes from 212.58.241.131: icmp_seq=2 ttl=246 time=7.39 ms
64 bytes from 212.58.241.131: icmp_seq=3 ttl=246 time=7.61 ms
64 bytes from 212.58.241.131: icmp_seq=4 ttl=246 time=7.27 ms
64 bytes from 212.58.241.131: icmp_seq=5 ttl=246 time=7.55 ms

So you should be seeing sub 10 ms pings to that BBC address if it is fed from a DC or Ethernet Fibre just like Yaz demonstrated.

cheers

In reply to a post by Yaz:

From my VFast connection (24mbit down / 10mbit up)

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=8ms TTL=55
Reply from 212.58.244.68: bytes=32 time=7ms TTL=55
Reply from 212.58.244.68: bytes=32 time=8ms TTL=55
Reply from 212.58.244.68: bytes=32 time=8ms TTL=55
Reply from 212.58.244.68: bytes=32 time=7ms TTL=55
Reply from 212.58.244.68: bytes=32 time=7ms TTL=55
Reply from 212.58.244.68: bytes=32 time=8ms TTL=55
Reply from 212.58.244.68: bytes=32 time=6ms TTL=55
Reply from 212.58.244.68: bytes=32 time=7ms TTL=55
Reply from 212.58.244.68: bytes=32 time=6ms TTL=55

Ping statistics for 212.58.244.68:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 7ms

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 3 ms 3 ms 3 ms 202.88.80.arpa.orbital.net [80.88.202.20]
3 3 ms 4 ms 4 ms 202.88.80.arpa.orbital.net [80.88.202.19]
4 6 ms 6 ms 7 ms ge0.ln1.thn.orbital.net [80.88.216.113]
5 8 ms 9 ms 9 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 16 ms 10 ms 8 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
8 8 ms 11 ms 14 ms 132.185.255.165
9 7 ms 8 ms 6 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

In reply to a post by kijoma:

hi,

those do look like ADSL pings to me Zyborg.

pings here from 3 customer locations on three different Fixed Wireless networks o you should be seeing sub 10 ms pings to that BBC address if it is fed from a DC or Ethernet Fibre just like Yaz demonstrated.

Not too bothered, Maybe it is because my supplier uses another ISP, which they do ZEN.

I don't think the pings will make that much difference. i do notice that speed can make pings faster.

a mate of mine on the same network as I was on but can get 16megabits, could get pings around the 12-15 mark and yet I was on 3.5 megabits and was lucky to get below 30. i suppose it would make a bit of a difference, but I did not think it would make that much.