In reply to a post by driz:

I ping New York at about 75ms from home I think. Be connection with fastpath in London and a 5ms first hop. Fibre might help me drop 4ms off that, though from the traceroutes I've seen from people on the BT trial, they still have a 4ms first hop.

I'd be very surprised (but pleased to hear) if it was that low. Using pingtest.net I get approximately 120ms at best (or to an east coast EC2 instance the same).

75ms to US not unreasonable, and have seen Be users with pings to our servers in london with an average of around the 7ms mark, i.e. a lot lower than most ISP's

In reply to a post by driz:

I ping New York at about 75ms from home I think. Be connection with fastpath in London and a 5ms first hop. Fibre might help me drop 4ms off that, though from the traceroutes I've seen from people on the BT trial, they still have a 4ms first hop.

Sounds unlikely - typical trans-atlantic routes from London to NY will be near 70ms and at best might achieve 60ms Add in you links though to that, plus routing in NY to the target will add 20-25ms

Can you provide a screenshot of from PingPlotter to prove me wrong?

Edited by MHC (Thu 15-Sep-11 11:12:34)

What would you expect for the specific London Telehouse/Telecity to the NY equivalent? We always worked on 75 to 80ms and we had several Gigabits of capacity on various links.

In reply to a post by MrSaffron:

75ms to US not unreasonable, and have seen Be users with pings to our servers in london with an average of around the 7ms mark, i.e. a lot lower than most ISP's

Many of them could plausibly have only been a short distance away from your test servers though.

For instance, given that using an expensive high priority business service from Verizon designed for low transatlantic latency achieved at best 78ms it seems unlikely to me.

http://www.verizonbusiness.com/about/network/latency/

In reply to a post by MHC:

Sounds unlikely - typical trans-atlantic routes from London to NY will be near 70ms and at best might achieve 60ms Add in you links though to that, plus routing in NY to the target will add 20-25ms

Can you provide a screenshot of from PingPlotter to prove me wrong?

I can't do that right now (as I'm at work), but here's a traceroute from a VPS in London:

traceroute to qw.quakephil.com (69.31.82.226), 30 hops max, 60 byte packets
1 212.111.33.229 (212.111.33.229) 0.790 ms 0.833 ms 0.874 ms
2 212.111.33.233 (212.111.33.233) 1.287 ms 1.342 ms 1.425 ms
3 te3-1-border76-01.lon2.telecity.net (217.20.44.217) 0.949 ms * *
4 * * *
5 195.50.113.1 (195.50.113.1) 0.998 ms 1.033 ms 1.026 ms
6 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 1.365 ms 1.174 ms 0.934 ms
7 ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 69.617 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 69.652 ms ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 69.618 ms
8 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 70.262 ms ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 79.120 ms 79.063 ms
9 ae-23-70.car3.NewYork1.Level3.net (4.69.155.69) 70.354 ms 70.310 ms 70.301 ms
10 PILOSOFT-IN.car3.NewYork1.Level3.net (4.53.88.10) 69.506 ms 69.722 ms 70.086 ms
11 69.172.128.1 (69.172.128.1) 70.068 ms 69.957 ms 69.941 ms
12 qw.quakephil.com (69.31.82.226) 69.807 ms 70.283 ms 70.066 ms

And here's my ping to bbc.co.uk from home (which I have saved in email drafts ;p)

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250

I can hopefully combine the two about 630pm tonight!

In reply to a post by driz:

In reply to a post by MHC:

Sounds unlikely - typical trans-atlantic routes from London to NY will be near 70ms and at best might achieve 60ms Add in you links though to that, plus routing in NY to the target will add 20-25ms

Can you provide a screenshot of from PingPlotter to prove me wrong?

I can't do that right now (as I'm at work), but here's a traceroute from a VPS in London:

traceroute to qw.quakephil.com (69.31.82.226), 30 hops max, 60 byte packets
1 212.111.33.229 (212.111.33.229) 0.790 ms 0.833 ms 0.874 ms
2 212.111.33.233 (212.111.33.233) 1.287 ms 1.342 ms 1.425 ms
3 te3-1-border76-01.lon2.telecity.net (217.20.44.217) 0.949 ms * *
4 * * *
5 195.50.113.1 (195.50.113.1) 0.998 ms 1.033 ms 1.026 ms
6 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 1.365 ms 1.174 ms 0.934 ms
7 ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 69.617 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 69.652 ms ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 69.618 ms
8 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 70.262 ms ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 79.120 ms 79.063 ms
9 ae-23-70.car3.NewYork1.Level3.net (4.69.155.69) 70.354 ms 70.310 ms 70.301 ms
10 PILOSOFT-IN.car3.NewYork1.Level3.net (4.53.88.10) 69.506 ms 69.722 ms 70.086 ms
11 69.172.128.1 (69.172.128.1) 70.068 ms 69.957 ms 69.941 ms
12 qw.quakephil.com (69.31.82.226) 69.807 ms 70.283 ms 70.066 ms

And here's my ping to bbc.co.uk from home (which I have saved in email drafts ;p)

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250
Reply from 212.58.241.131: bytes=32 time=5ms TTL=250

I can hopefully combine the two about 630pm tonight!

That is cheating . Running from a data centre directly to another data centre. I was talking about home grade bb connections.

In reply to a post by dustofnations:

That is cheating . Running from a data centre directly to another data centre. I was talking about home grade bb connections.

Yeah, but I ping the bbc datacentre at 5ms from home. So the theory (and practice, I'm fairly sure!) goes that I get about 75ms from home to NY!

But you'll have to wait 7 hours

In reply to a post by MrSaffron:

75ms to US not unreasonable, and have seen Be users with pings to our servers in london with an average of around the 7ms mark, i.e. a lot lower than most ISP's

On a somewhat related note (more to do with the OP before it was deleted). Have you tried to get an interview with these HyperOptic guys to see what they're supposedly up to? It'd be nice to hear some real technical details from them rather than marketing fluff which is pretty much useless.

I'd like to hear proper information about their IPv6 support, how they intend to support such huge bandwidth connections, what real world speeds people should expect during peak times, what their peering arrangements are given the massive connection speeds.

Other nice info would be national vs international bandwidth. For instance some fast ISPs abroad give high speeds within the country and more limited speed internationally (for obvious costs reasons).

If large numbers of home users suddenly had gigabit connections and hammered them, even LINX would fall on its face!

Edit: They don't even seem to be on the LINX members list, I'd have expected to see them there by now as they are supposedly beginning to connect people up.

Edited by deleted (Thu 15-Sep-11 12:13:37)

So where is the server in the US? I must be co-located with the transatlantic termination.

One of the NY terminations that our traffic would flow through is 195.66.224.130 currently that is giving an average of 94ms which if I remove the 12ms to get to the UK end still gives 82 ...


And looking at your figures again, you must be in one of the London centres - so 70 ms is what I suggest for the transatlantic hop.

It is a little better than one I was using last week - San Diego to TBB was around 700ms !

Edited by MHC (Thu 15-Sep-11 11:28:39)