[dragon]

Here's the results.

From: smaugy

Reply from 82.133.85.65: bytes=32 time=30ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=28ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=30ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54

Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 30ms, Average = 29ms

From rich1068 (pinged CF by mistake)

Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=40ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Ping statistics for above hosts:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 39ms

From: matt-s

I'm NOT on fastpath and I get a ping of 38ms too. Would have thought the fastpath guys should get less?

From: Siteguru

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=40ms TTL=53
Reply from 82.133.85.65: bytes=32 time=36ms TTL=53
Reply from 82.133.85.65: bytes=32 time=36ms TTL=53
Reply from 82.133.85.65: bytes=32 time=38ms TTL=53

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

Additonal Notes: Via wi-fi


From: ntriantafyllou

am on fastpath Annex M - up 2,169 / down 18,835 - Shoreditch Exchange

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51

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

From: gillyallan

I sync around 22,500 on fastpath. Live in Central Scotland


Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=38ms TTL=53

Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 38ms, Average = 34ms

Thanks to the people at the BE forums.