OT: US ping times

[Dave Liquorice]

What's the normal ping time to a machine in the US?

Seems the hop across the pond is adding a good 150 ms these days, I always thought it only added a few 10's of ms.

[Mike Tomlinson]

En el artículo , Dave Liquorice escribió:

Which coast? Serious question - pings from Blighty to east coast can be much lower than to west.

[Andrew Gabriel]

I'm getting to NY and back in 86ms over ADSL, of which 50ms is the transatlantic hop (which is about right for ~8000km).

What does a traceroute look like for you?

[Andy Burns]

My ISP is plusnet, so upstream routing tends to be via BT as their parent, the UK/US hop of a tracert adds under 70ms

6 19 ms 19 ms 18 ms 166-49-211-228.eu.bt.net [166.49.211.228] 7 85 ms 85 ms 86 ms ixp1-xe-1-0-0-0.us-nyc.eu.bt.net [166.49.208.41]

[Graeme]

In message , Dave Liquorice writes

This is google.co.uk

Host IP address = 216.58.214.3 From 216.58.214.3 : OK : trip time = 29 ms From 216.58.214.3 : OK : trip time = 27 ms From 216.58.214.3 : OK : trip time = 28 ms From 216.58.214.3 : OK : trip time = 26 ms From 216.58.214.3 : OK : trip time = 26 ms

PING statistics

5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 26/27/29

This is google.com

[translating host name to IP address] Host IP address = 172.217.23.46 From 172.217.23.46 : OK : trip time = 27 ms From 172.217.23.46 : OK : trip time = 27 ms From 172.217.23.46 : OK : trip time = 29 ms From 172.217.23.46 : OK : trip time = 28 ms From 172.217.23.46 : OK : trip time = 237 ms

PING statistics

5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 27/69/237

Having said that, I have no idea where either actually are.

[Andy Burns]

But google.com is distributed around the world and likely to use tricks like anycast to reach the closest instance to you, if your ISP is big enough to count, that IP address is likely to be in the ISPs datacentre, not Google's.

[Andy Burns]

For me (and it will vary) I assume the LHR airport code in the hostname means it's "somewhere in London"

C:> nslookup 172.217.23.46

Name: lhr35s02-in-f46.1e100.net Address: 172.217.23.46

[Andrew Gabriel]

27ms is only 8100km at speed of light, which won't get you to the East Coast and back, so it's certainly a location nearer than the US.

[Andy Burns]

My FTTC connection takes ~18ms to reach my ISP's datacentre, from there a lot popular content will be via content farms on fat 10gig pipes.

So a *LOT* of the internet appears to be 20ms away :-)

e.g.

C:\ >tracert -d

Tracing route to

[212.56.71.103] over a maximum of 30 hops:

1 1 ms 192.168.1.1 2 19 ms 195.166.128.195 3 19 ms 212.159.2.144 4 19 ms 212.159.0.240 5 18 ms 195.166.129.5 6 18 ms 195.166.129.3 7 18 ms 212.56.71.103

Trace complete.

[Adrian Caspersz]

Except HP, for downloads from their support website try next week or move to the moon where their servers obviously are...

[The Natural Philosopher]

I had to recheck that and yes, you are right.

By the way. Delay is normally dominated by the pipe *speed* and packet length as much as the propagation delay of a signal.

I.e at 1bps it takes 8x1500 seconds to transmit and reassemble a 1500 byte IP packet= 12000 seconds

At 1kbps it takes 12 seconds

at 448kbps its 26 ms.

Add in 10% for the downlink and you can see that a round trip delay of

27 ms or so is the minimum an ADSL 2 connection will do,

Looking at the target IP address above, it loks like it goes no futher than Telehouse UK

[Mike Tomlinson]

En el artículo , Andrew Gabriel escribió:

C:\Users\mike>tracert

Tracing route to

[216.58.213.100] over a maximum of 30 hops:

1

[dennis]

Its quite hard to actually get to a site in the US..

I did a trace route for mit.edu but it doesn't appear to be in the states.

Tracing route to mit.edu [2a02:26f0:59:180::255e] over a maximum of 30 hops:

1 6 ms 5 ms 5 ms 2a02:c7f:b816:fa00::1 2 * * * Request timed out. 3 14 ms 17 ms 93 ms xe-11-0-1.edge5.London1.Level3.net [2001:1900:5:2:2::d59] 4 15 ms 14 ms 13 ms xe-11-0-1.edge5.London1.Level3.net [2001:1900:5:2:2::d59] 5 29 ms 56 ms 97 ms vl-4045.edge3.London1.Level3.net [2001:1900:5:1::412] 6 16 ms 15 ms 18 ms vl-51.edge5.London1.Level3.net [2001:1900:101:1::a] 7 16 ms 15 ms 16 ms ldn-b5-link.telia.net [2001:2000:3080:97::1] 8 14 ms 20 ms 13 ms ldn-b5-v6.telia.net [2001:2000:3018:b::1] 9 18 ms 14 ms 14 ms akamai-ic-153470-ldn-b5.c.telia.net [2001:2000:3080:4eb::2] 10 16 ms 15 ms 14 ms 2a02:26f0:59:180::255e

[Andy Burns]

Actually hpe.com was one of the sites I traced to and like bbc, amazon, ebay they were all 18ms away.

[Mike Tomlinson]

En el artículo , dennis@home.? escribió:

The older unis are usually a good bet. This is Uni of Califonia at Berkeley, on the west coast.

C:\Users\mike>tracert berkeley.edu

Tracing route to berkeley.edu [128.32.203.137] over a maximum of 30 hops:

1

[Bob Martin]

I get 145 ms from my website host in Texas.

[Dave Liquorice]

Sorry guys asked the question then did somthing to the relative positions of the L4 nerve and muscles(*) in my back triggering severe pain/numbness in my right leg. Barely able to move for a couple of days...

So 170 ms is about right for the west coast. I hadn't thought of propergation delay in terrestial circuits. 3x10^8 m/s = 3*10^5 m/ms =

300 km/ms, probably shorter per ms in reality as the light isn't traveling in freespace but glass.

(*) Doesn't appear to be a herniated disc as the back moves fine without triggering any pain in it or the leg.