ADSL24 - Packet Loss somewhere in the London Tube Exchanges?

I know there's been some problems at Telehouse North over the past week but am I the only ADSL24 customer still suffering from varying degrees of packet loss:

[root@tux1g ~]# traceroute www.twitter.com
traceroute to www.twitter.com (199.59.148.10), 30 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 3.092 ms 3.064 ms 3.048 ms
2 lns6.uan.thn.uk.murphx.net (89.145.254.85) 39.989 ms 41.546 ms 41.549 ms
3 uan-er1.uan.thn.uk.murphx.net (89.145.254.65) 43.432 ms 43.457 ms 44.913 ms
4 ge2-6-1.cr2.core.thn.uk.murphx.net (89.145.254.169) 44.919 ms 46.094 ms 46.103 ms
5 ge1-2-1.crs1.core.thn.uk.murphx.net (109.170.249.45) 47.482 ms 49.052 ms 49.059 ms
6 te2-3.cr05.tn5.bb.gxn.net (62.72.139.97) 50.487 ms 41.207 ms 41.208 ms
7 ge-0.linx.london03.uk.bb.gin.ntt.net (195.66.224.138) 42.546 ms 40.498 ms 40.507 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

Example 2:

traceroute www.uk2.net
traceroute to www.uk2.net (83.170.69.14), 30 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 3.105 ms 3.056 ms 3.040 ms
2 lns6.uan.thn.uk.murphx.net (89.145.254.85) 39.465 ms 41.396 ms 42.708 ms
3 uan-er1.uan.thn.uk.murphx.net (89.145.254.65) 42.717 ms 42.726 ms 44.489 ms
4 ge2-6-1.cr2.core.thn.uk.murphx.net (89.145.254.169) 46.022 ms 46.025 ms 47.372 ms
5 ge1-2-1.crs1.core.thn.uk.murphx.net (109.170.249.45) 47.380 ms 47.391 ms 48.781 ms
6 te2-3.cr05.tn5.bb.gxn.net (62.72.139.97) 50.295 ms 40.187 ms 40.192 ms
7 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 42.271 ms 40.231 ms 40.233 ms
8 * * *
9 83.170.70.234 (83.170.70.234) 44.230 ms 46.667 ms 46.686 ms
10 dc5.as13213.net (83.170.70.138) 46.688 ms 46.697 ms dc5.as13213.net (83.170.70.134) 48.701 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

Router's been powered off for 20+ mins several times. I have a ticket open with ADSL24.

Am I alone in my suffering?!

That looks more like the server you are tracing to is not responding to ping/trace rather than actual packet loss

What happens if you tracert www.thinkbroadband.com

And a router in the middle that is set to not respond.

Matt

I'm on ADSL24 (fibre), in Oxfordshire, if this helps.

Here is my route to www.thinkbroadband.com as suggested.


Tracing route to www.thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 11 ms 11 ms 12 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 12 ms 11 ms 12 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 11 ms 11 ms 11 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.169]
5 11 ms 11 ms 11 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249.45]
6 14 ms 12 ms 11 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 13 ms 13 ms 13 ms lonap-gw1.thdo.ncuk.net [5.57.80.142]
8 13 ms 12 ms 13 ms gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
9 11 ms 12 ms 12 ms www.thinkbroadband.com [80.249.99.130]

For completeness, my twitter.com trace:

Tracing route to twitter.com [199.59.150.7]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 11 ms 11 ms 11 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 11 ms 11 ms 11 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 11 ms 11 ms 11 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161]
5 11 ms 12 ms 12 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
6 13 ms 12 ms 14 ms ge-0.linx.london03.uk.bb.gin.ntt.net [195.66.224.138]
7 12 ms 12 ms 11 ms ae-1.r02.londen03.uk.bb.gin.ntt.net [129.250.5.25]
8 86 ms 94 ms 87 ms twitter-0.r02.londen03.uk.bb.gin.ntt.net [213.130.48.90]
9 86 ms 86 ms 86 ms xe-1-2-1.iad-cr2.twttr.com [199.16.159.125]
10 154 ms 154 ms 153 ms ae60.pao1-cr2.twttr.com [199.16.159.87]
11 160 ms 161 ms 161 ms ae51.smf1-er1.twttr.com [199.16.159.29]
12 158 ms 157 ms 159 ms r-199-59-150-7.twttr.com [199.59.150.7]

Thanks everyone - all sorted now.

It seemed to be an issue with a small IP block.

During the fix the back-room guys managed to 'lose' my fixed IP address and put me into a DHCP pool, but I am now back on a static IP (...a different one..mutter mutter..DNS changes...) and things are routing properly.

Have to say the ADSL24 support guys were doing their best and this seemed to be an upstream issue/cock-up.

So there is no longer any "packet loss" on the Underground?

Those twits in USA are far away.