Packetloss on BT ADSL

[Aravis]

Have been getting a lot of packetloss for the last two nights. The PLF meter usually showing Yellow on the L icon.

Tracing route to 193.252.123.24 over a maximum of 30 hops

1 65 ms 49 ms 19 ms bthg303-hg2.bletchley.broadband.bt.net [217.32.61.201]
2 28 ms 65 ms 30 ms 217.32.61.130
3 39 ms 59 ms 66 ms 217.32.61.238
4 29 ms 33 ms 50 ms inh2cs01-603.imsnet2.btopenworld.com [62.7.251.129]
5 40 ms 45 ms 61 ms 213.120.62.201
6 22 ms 30 ms 50 ms core2-pos12-3.bletchley.ukcore.bt.net [194.72.31.45]
7 * 42 ms 43 ms core2-pos5-3.ilford.ukcore.bt.net [194.74.65.233
]
8 93 ms 70 ms 83 ms transit1-pos4-0.ilford.ukcore.bt.net [194.72.20.230]
9 31 ms 30 ms 26 ms transit1-pos6-0.tufnell.ukcore.bt.net [194.72.20.142]
10 327 ms * 323 ms t2a4-p9-0.uk-lon2.concert.net [166.49.209.13]
11 310 ms 303 ms 282 ms t2c1-ge6-0.uk-lon2.concert.net [166.49.176.11]
12 304 ms 289 ms 298 ms t2c1-ge1-2.uk-lon1.concert.net [166.49.208.242]

13 327 ms 284 ms 338 ms 166-49-211-2.concert.net [166.49.211.2]
14 299 ms 312 ms 305 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.25
1.154.225]
15 321 ms 314 ms * P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
16 313 ms 314 ms 322 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
17 336 ms 309 ms 360 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
18 * 302 ms 289 ms 193.252.122.10
19 285 ms 281 ms 307 ms 193.252.123.24

Trace complete.

Tracing route to 193.252.123.24 over a maximum of 30 hops

1 51 ms 32 ms 32 ms bthg303-hg2.bletchley.broadband.bt.net [217.32.61.201]
2 32 ms 62 ms 32 ms 217.32.61.130
3 51 ms 34 ms 31 ms 217.32.61.238
4 40 ms 33 ms 32 ms inh2cs01-603.imsnet2.btopenworld.com [62.7.251.129]
5 58 ms 31 ms 29 ms 213.120.62.201
6 66 ms 62 ms 20 ms core2-pos12-3.bletchley.ukcore.bt.net [194.72.31.45]
7 33 ms 28 ms 24 ms core2-pos5-3.ilford.ukcore.bt.net [194.74.65.233]
8 68 ms 40 ms 43 ms transit1-pos4-0.ilford.ukcore.bt.net [194.72.20.230]
9 54 ms 24 ms 30 ms transit1-pos6-0.tufnell.ukcore.bt.net [194.72.20.142]
10 262 ms 315 ms 258 ms t2a4-p9-0.uk-lon2.concert.net [166.49.209.13]
11 275 ms * 344 ms t2c1-ge6-0.uk-lon2.concert.net [166.49.176.11]
12 248 ms 271 ms 251 ms t2c1-ge1-2.uk-lon1.concert.net [166.49.208.242]

13 273 ms 267 ms 284 ms 166-49-211-2.concert.net [166.49.211.2]
14 272 ms 302 ms 290 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]
15 299 ms 298 ms 285 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
16 267 ms 277 ms 274 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
17 295 ms 276 ms 313 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
18 290 ms 298 ms 290 ms 193.252.122.10
19 278 ms 274 ms 275 ms 193.252.123.24

Trace complete.

Tracing route to 193.252.123.24 over a maximum of 30 hops

1 35 ms 21 ms 19 ms bthg303-hg2.bletchley.broadband.bt.net [217.32.61.201]
2 20 ms 18 ms 19 ms 217.32.61.130
3 31 ms 24 ms 29 ms 217.32.61.238
4 39 ms 38 ms 37 ms inh2cs01-603.imsnet2.btopenworld.com [62.7.251.129]
5 48 ms 53 ms 47 ms 213.120.62.201
6 60 ms 50 ms 64 ms core2-pos12-3.bletchley.ukcore.bt.net [194.72.31.45]
7 35 ms 61 ms 41 ms core2-pos5-3.ilford.ukcore.bt.net [194.74.65.233]
8 30 ms 25 ms 25 ms transit1-pos4-0.ilford.ukcore.bt.net [194.72.20.230]
9 50 ms 35 ms 38 ms transit1-pos6-0.tufnell.ukcore.bt.net [194.72.20.142]
10 * 297 ms * t2a4-p9-0.uk-lon2.concert.net [166.49.209.13]
11 * 278 ms 299 ms t2c1-ge6-0.uk-lon2.concert.net [166.49.176.11]
12 274 ms 265 ms 299 ms t2c1-ge1-2.uk-lon1.concert.net [166.49.208.242]

13 325 ms 274 ms 271 ms 166-49-211-2.concert.net [166.49.211.2]
14 326 ms 284 ms 263 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]
15 282 ms 305 ms 355 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
16 299 ms 282 ms 283 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
17 303 ms 283 ms 289 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
18 282 ms 304 ms 308 ms 193.252.122.10
19 270 ms 265 ms 266 ms 193.252.123.24

Trace complete.

Big jump in ping at concert.net and usually a bit of ploss there.
Not completely unplayable but making it very hard to get reactive styles off...

 

[Jonaldo]

This is a very common issue between BT & the Wannadoo servers

Got the same problem myself and many others also.

A week or so ago we were ld'ing every few seconds and it was totally unplayable, one time I was ok in one zone yet LD every time I stepped foot in Tur Suil Dungeon (Hybrasil).

Not sure what's wrong but it looks like the only thing we can do is sit and wait for it to get sorted.

 

[Aravis]

Reported it to BT (and GOA but to be fair there is little they can do about it) and....

it seems to be sorted!

Down from 3-400 ping to nearer 30-40 so a lot easier to get those reactives off

Forgot to mention, concert.net is part of BT Ignite so if it happens again it is worth emailing BT support.