9ms ping time over internet! (er.. wow!)

LOL some of this WAN performance is better than my internal network.

Laptop over wifi to BT home hub 5 (GW)

Code: 
Ping statistics for 192.168.1.1:
    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 5ms, Average = 2ms

Laptop over wifi to NAS via TP-Link 500Mbps homeplugs.
Code: 
Ping statistics for 192.168.1.253:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 16ms, Average = 6ms

Laptop over wifi to Multiplay to show WAN latency (BT Infinity, based in cardiff).
Code: 
Ping statistics for 85.236.96.26:
    Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 17ms, Average = 14ms
 
My desk top to Multiplay (using Powerline Ethernet to my router and then on to BT Infinity):

Pinging multiplay.co.uk [85.236.96.26] with 32 bytes of data:
Reply from 85.236.96.26: bytes=32 time=9ms TTL=54
Reply from 85.236.96.26: bytes=32 time=9ms TTL=54
Reply from 85.236.96.26: bytes=32 time=9ms TTL=54
Reply from 85.236.96.26: bytes=32 time=9ms TTL=54

Ping statistics for 85.236.96.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms
Click to expand...
 
PING multiplay.co.uk (85.236.96.26): 56 data bytes
64 bytes from 85.236.96.26: icmp_seq=0 ttl=59 time=0.721 ms
64 bytes from 85.236.96.26: icmp_seq=1 ttl=59 time=0.698 ms
64 bytes from 85.236.96.26: icmp_seq=2 ttl=59 time=0.729 ms
64 bytes from 85.236.96.26: icmp_seq=3 ttl=59 time=0.724 ms
64 bytes from 85.236.96.26: icmp_seq=4 ttl=59 time=0.716 ms
Click to expand...

;)
 
You must log in or register to reply here.
Back
Top Bottom