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

HEADRAT · 31 Oct 2015 at 07:36

KIA said:
Speed of light.

Yep, until somebody "can break the laws of physics" we're stuck with 299 792 458 m / s

The amount of arguments I've had with people in "Management" about latency vs bandwidth is amazing

Adding more bandwidth != to lower latency, it's a long way to the West Coast of the U.S. however much bandwidth you throw at it!

The best way improve QOS is to bring "content" as close to the "eyeballs" as possible

nutcase · 31 Oct 2015 at 11:17

Not sure where it's hosted but I can ping whitehouse.gov in 8ms. Pretty sure that will be in the states somewhere. That's quite impressive.

Craig321 · 31 Oct 2015 at 11:22

nutcase_1uk said:
Not sure where it's hosted but I can ping whitehouse.gov in 8ms. Pretty sure that will be in the states somewhere. That's quite impressive.

They use Akamai (distribution network) so would route you into the UK.

nutcase · 31 Oct 2015 at 15:03

Boring!

But that does make sense. Did seem rather quick.

NightSt@lk3r · 31 Oct 2015 at 18:01

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

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

It's ok i guess for bog standard living in the woods ADSL.

Scougar · 31 Oct 2015 at 19:21

Craig321 said:
They use Akamai (distribution network) so would route you into the UK.

(They also do caching). We use them.

Jez · 1 Nov 2015 at 08:41

9ms doesn't seem anything to write home about, any bog standard vdsl connection should manage this to a destination with not too many hops

Yep, just tested mine, I get between 8-10 to google on mine out in the Oxfordshire countryside...

ScoTTyBEEE · 2 Nov 2015 at 17:20

I think the light bounces around in fibre cables off the 'walls' inside it. When they can ensure a straight line then the pings to the US will improve.

Rroff · 2 Nov 2015 at 17:23

ScoTTyBEEE said:
I think the light bounces around in fibre cables off the 'walls' inside it. When they can ensure a straight line then the pings to the US will improve.

When they put the new link from London to New York in around 2004 IIRC I was pinging under 70ms to east coast US game servers until traffic levels picked up - fairly quickly went to 109ms with more traffic on the link and mid 120s last time I checked :S (That was from London with a sub 4ms latency to sites hosted in telehouse, etc.)

LizardKing · 2 Nov 2015 at 17:58

Do we win anything

Kreeeee · 2 Nov 2015 at 18:11

I get 5-7ms back home.

OllyM · 2 Nov 2015 at 21:16

Rroff said:
When they put the new link from London to New York in around 2004 IIRC I was pinging under 70ms to east coast US game servers until traffic levels picked up - fairly quickly went to 109ms with more traffic on the link and mid 120s last time I checked :S (That was from London with a sub 4ms latency to sites hosted in telehouse, etc.)

Going the other way my ping to the BBC is just over 70ms.

--- bbc.co.uk ping statistics ---
23 packets transmitted, 23 received, 0% packet loss, time 22028ms
rtt min/avg/max/mdev = 71.668/72.252/74.135/0.623 ms

Oh and..

--- google.com ping statistics ---
23 packets transmitted, 23 received, 0% packet loss, time 22030ms
rtt min/avg/max/mdev = 2.770/3.714/4.833/0.615 ms

On Verizon FiOS FTTP.

nutcase · 2 Nov 2015 at 21:22

From work (Enta 15mbit fibre):

Pinging 85.236.96.26 with 32 bytes of data:
Reply from 85.236.96.26: bytes=32 time=4ms TTL=52
Reply from 85.236.96.26: bytes=32 time=4ms TTL=52
Reply from 85.236.96.26: bytes=32 time=4ms TTL=52
Reply from 85.236.96.26: bytes=32 time=4ms TTL=52

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

Scougar · 3 Nov 2015 at 02:33

Awesome times. Never realized internet connections had got so good.

Rroff · 3 Nov 2015 at 02:50

Scougar said:
Awesome times. Never realized internet connections had got so good.

Its been quite different for the US compared to the UK mind (I played Quake 3 in the US back in the day so know a bit about the connection quality there) whereas the UK being smaller if you were on a half decent ADSL connection you'd see fairly decent latency unless you lived somewhere really remote.

The big improvements of late has been the reduction in latency for those in more remote parts rather than in the cities where its typically been good.

Steveocee · 3 Nov 2015 at 20:35

Wireless from my laptop over a fixed wireless link (Yes I use a WISP. Pfffft to all you copper huggers)

Code:

PING multiplay.co.uk (85.236.96.26) 56(84) bytes of data.

64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=1 ttl=55 time=15.6 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=2 ttl=55 time=15.0 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=3 ttl=55 time=13.7 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=4 ttl=55 time=14.6 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=5 ttl=55 time=14.6 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=6 ttl=55 time=15.0 ms
^C
--- multiplay.co.uk ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 13.796/14.804/15.617/0.574 ms

Steveocee · 3 Nov 2015 at 20:38

And this is from my server in colo;

Code:

PING multiplay.co.uk (85.236.96.26) 56(84) bytes of data.
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=1 ttl=57 time=11.6 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=2 ttl=57 time=11.6 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=3 ttl=57 time=11.5 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=4 ttl=57 time=11.7 ms
64 bytes from ha01.multiplay.co.uk (85.236.96.26): icmp_seq=5 ttl=57 time=11.8 ms
^C
--- multiplay.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 11.507/11.672/11.822/0.161 ms

Rroff · 4 Nov 2015 at 01:52

Oh wow BT has seriously optimised routing to multiplay - used to be 15-16 hops

Tracing route to multiplay.co.uk [85.236.96.26]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * 7 ms 31.55.187.177
4 8 ms 8 ms 7 ms 31.55.187.176
5 7 ms 7 ms 6 ms core2-hu0-8-0-5.southbank.ukcore.bt.net [195.99.
127.186]
6 7 ms 8 ms 7 ms peer1-et-2-1-0.telehouse.ukcore.bt.net [62.172.1
03.25]
7 8 ms 8 ms 8 ms linx1.multiplay.co.uk [195.66.224.224]
8 8 ms 8 ms 8 ms ha01.multiplay.co.uk [85.236.96.26]

Trace complete.

darkblade · 5 Nov 2015 at 11:06

ScoTTyBEEE said:
I think the light bounces around in fibre cables off the 'walls' inside it. When they can ensure a straight line then the pings to the US will improve.

That's how fibre is supposed to work - reflecting a lightwave does not slow it down - however it does have to travel a longer distance, which does take longer.

It's also very difficult to have a straight line from the UK to the US when you take the curvature of the earth into consideration.

On Holiday · 5 Nov 2015 at 13:10

Screeeech said:
9ms? ppffffff..

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

Traceroute would be more interesting..