Latency 20/08/2008

neocr0n · Aug 20, 2008, 15:14:55

Latency is appauling today being pinging 100+ all morning. So has my friend also IDnet and on the same exchange.

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data

Reply from 212.58.224.131: bytes=32 time=1898ms TTL=121
Reply from 212.58.224.131: bytes=32 time=137ms TTL=121
Reply from 212.58.224.131: bytes=32 time=132ms TTL=121
Reply from 212.58.224.131: bytes=32 time=100ms TTL=121

Both from the North East, anyone else have poor latency today?

Rik · Aug 20, 2008, 15:18:49

Slower than normal here:

ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:

Reply from 212.58.253.67: bytes=32 time=85ms TTL=122
Reply from 212.58.253.67: bytes=32 time=111ms TTL=122
Reply from 212.58.253.67: bytes=32 time=96ms TTL=122
Reply from 212.58.253.67: bytes=32 time=110ms TTL=122

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

I suspect it relates to the 'Olympic congestion' being discussed here.

tomharrison · Aug 20, 2008, 15:22:52

Seems about normal for me:

Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=26ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=27ms TTL=121

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

Throughput is getting bad again though (sub 2Mbps as opposed to 4Mb), however nowhere near like the 300kbps I was getting last night!

On GW5 if that helps.

Rik · Aug 20, 2008, 15:26:09

Interesting, you'd be on GW5 I guess, Tom, whereas I'm on DSL4, as I think neocr0n is.

neocr0n · Aug 20, 2008, 15:51:09

Yeah I'm on DSL4 also Rik. Olympic congestion really? It's being largely fine since the Olympics started. It's just today that its not too hot.

Ah well I'll hold out till after the Olympics and see if it settles down. I hope thats all the problem is, far better than an actuall technical problem. Speaking of the Olympics, Usain Bolt! guy's crazy fast!

Rik · Aug 20, 2008, 15:56:01

The Olympic effect is building, as you'll see in the other thread, and it's only just beginning to bite. Some of it is site, I am sure, as pinging idnet.net produced 23-26ms responses, it would be useful if you could try that please.

I'm hoping Bolt doesn't turn out to be using drugs, he's amazing.

Baz · Aug 20, 2008, 17:24:42

Im in north east too and on gw5 got this result.

Reply from 212.58.224.131: bytes=32 time=31ms TTL=122
Reply from 212.58.224.131: bytes=32 time=27ms TTL=122
Reply from 212.58.224.131: bytes=32 time=26ms TTL=122
Reply from 212.58.224.131: bytes=32 time=26ms TTL=122

Rik · Aug 20, 2008, 17:34:11

Thanks, Baz. I'm half wondering whether there's a load balancing issue between DSL4 and GW5. I've raised it with IDNet.

neocr0n · Aug 20, 2008, 18:51:58

It's blanced out now back to 30, I only used bbc.co.uk as an example on here Rik I had checked other sites and gaming servers first. It was definatly bad all round.

Anyway back to normal thanks fellas

Rik · Aug 20, 2008, 18:53:06

I know IDNet took a look, perhaps they gave something a good talking to.

neocr0n · Aug 21, 2008, 16:35:32

Same again today, do I really have to endure this untill the end of the olympics? DSL4. I don't know all the inner workings of networks and the internet and what not but I find it very hard to believe very hard indeed that everyone in the North East with internet is streaming the olympics via BBC when BBC have it on TV. Especially during the day when people are at work anyway. I'm not buying this Olympics nonsense.

Rik · Aug 21, 2008, 16:40:24

It's true, we've seen the graphs from Plusnet, I've seen the explanation from Zen and IDNet. Essentially, the BBC latency is because their site is being used heavily and the peering to them is near to full. OTOH, I haven't really noticed an impact in using the site. Others are less affected.

What may be happening, of course, is that the data centre you are routed though is also struggling to cope. As I live on top of one, maybe I'm less affected. Similarly, on the limited evidence I have, DSL4 is more affected than GW5, which may be down to a different routing.

All I can suggest is that you contact IDNet directly to see if they can identify a specific problem.

Glenn · Aug 21, 2008, 16:43:53

I'm pinging the BBC at an average of 31ms with 1 lost packet on dsl4, I'm in the south though.

Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=37ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=31ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=26ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=32ms TTL=121
Reply from 212.58.253.67: bytes=32 time=26ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=34ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=30ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=39ms TTL=121
Reply from 212.58.253.67: bytes=32 time=39ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=26ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=32ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=36ms TTL=121
Reply from 212.58.253.67: bytes=32 time=32ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Request timed out.
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=101ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=41ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=30ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=27ms TTL=121
Reply from 212.58.253.67: bytes=32 time=41ms TTL=121
Reply from 212.58.253.67: bytes=32 time=38ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=30ms TTL=121
Reply from 212.58.253.67: bytes=32 time=34ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=30ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=31ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=27ms TTL=121
Reply from 212.58.253.67: bytes=32 time=30ms TTL=121
Reply from 212.58.253.67: bytes=32 time=29ms TTL=121
Reply from 212.58.253.67: bytes=32 time=28ms
Ping statistics for 212.58.253.67:
Packets: Sent = 64, Received = 62, Lost = 2 (3% loss),
TTL=121
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 101ms, Average = 31ms

Rik · Aug 21, 2008, 16:46:06

I'm averaging 31ms today. Thanks for the extra input, Glenn.

Glenn · Aug 21, 2008, 16:47:23

It just got a little bit extra too

Steve · Aug 21, 2008, 16:59:00

This my typical tracert to xbox.com is this typical for sites across the pond? The slow response for 80.253.101.249 surprises me as its located in this country or is it just giving me a low priority on pings.

Indeed a tracert will often time out at this stage whether it be to xbox msn or microsoft.

2 103 ms 77 ms 56 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 35 ms 40 ms 38 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 39 ms 48 ms 34 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 115 ms 119 ms 120 ms 80.253.101.249
6 104 ms 103 ms 105 ms ge-0-3-0-55.nyc-64cb-1b.ntwk.msn.net [207.46.34.
125]
7 191 ms 178 ms 180 ms ge-0-1-0-0.co1-64c-1b.ntwk.msn.net [207.46.33.20
6]
8 181 ms 185 ms 184 ms ge-0-1-0-0.wst-64cb-1b.ntwk.msn.net [207.46.34.1
3]
9 297 ms 199 ms 183 ms vlan57.wst-76e-2.ntwk.msn.net [207.46.36.250]

Rik · Aug 21, 2008, 17:02:19

I'm timing out after redbus-gw2, Steve.

Glenn · Aug 21, 2008, 17:02:51

I get very similar results Steve

Rik · Aug 21, 2008, 17:08:13

Back to normal here too. There was a direct peering problem earlier this week, so IDNet are going to have another look at that.

Rik · Aug 21, 2008, 17:11:52

tracert www.xbox.com

Tracing route to xbox.com [65.59.234.166]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 25 ms 25 ms 29 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 48 ms 57 ms 51 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 23 ms 25 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 271 ms 204 ms 220 ms 80.253.101.249
6 102 ms 110 ms 100 ms ge-0-3-0-54.nyc-64cb-1a.ntwk.msn.net [207.46.36.13]
7 129 ms 110 ms 98 ms ge-0-0-0-0.nyc-64cb-1b.ntwk.msn.net [207.46.37.150]
8 99 ms 124 ms 114 ms ge-0-1-0-0.blu-64c-1b.ntwk.msn.net [207.46.33.121]
9 176 ms 181 ms 173 ms ge-7-1-0-0.wst-64cb-1b.ntwk.msn.net [207.46.34.177]
10 183 ms 171 ms 169 ms ge-7-0-0-0.wst-64cb-1a.ntwk.msn.net [207.46.34.121]
11 180 ms 179 ms 171 ms vlan54.wst-76e-1.ntwk.msn.net [207.46.36.170]

Gary · Aug 21, 2008, 17:13:49

Quote from: Rik on Aug 21, 2008, 16:46:06
I'm averaging 31ms today. Thanks for the extra input, Glenn.

Even though Im on a different ISP here is my ping to the bbc
bbc.net.uk

Pinging bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=25ms TTL=123
Reply from 212.58.253.67: bytes=32 time=24ms TTL=123
Reply from 212.58.253.67: bytes=32 time=24ms TTL=123
Reply from 212.58.253.67: bytes=32 time=24ms TTL=123

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

neocr0n · Aug 21, 2008, 17:23:56

I don't judge the performance of my connection on just my ping to bbc.

My ping to several gaming servers and communication servers are all naff and 100+ just like yesterday.

Rik · Aug 21, 2008, 17:33:09

All I can suggest is that you get IDNet to take a look at your connection, it may be an exchange or data centre issue.

Glenn · Aug 21, 2008, 17:37:55

Averaging around 110ms to 69.28.242.218 my rfactor server in Canada, it is approx 3500 - 4000 miles away as the crow flies its great circle.

psp83 · Aug 21, 2008, 17:46:23

C:\Users\Paul>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 14 ms 14 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 17 ms 15 ms 14 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 16 ms 14 ms 14 ms rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
5 14 ms 15 ms 34 ms 212.58.238.153
6 29 ms 15 ms 15 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
7 15 ms 16 ms 15 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.