Don't know. It was installed yesterday and I haven't got too involved with it yet. I was getting 5ms pings to some of the speedtest.net hosts earlier today if that's any indication.
just that your second hop is a little high.
Don't know. It was installed yesterday and I haven't got too involved with it yet. I was getting 5ms pings to some of the speedtest.net hosts earlier today if that's any indication.
just that your second hop is a little high.
C:\Users\Admin>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 65 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 21 ms 16 ms 16 ms lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
3 16 ms 15 ms 15 ms link10-central10.ptw-gw02.plus.net [84.93.248.82
]
4 15 ms 15 ms 15 ms xe-7-2-0.ptw-cr02.plus.net [212.159.1.22]
5 16 ms 15 ms 16 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 16 ms 15 ms 16 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
7 * * * Request timed out.
8 16 ms 58 ms 16 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
9 17 ms 16 ms 18 ms 132.185.255.60
10 15 ms 16 ms 15 ms 212.58.241.131
Trace complete.
C:\Users\Admin>
just that your second hop is a little high.
As above I had Plusnet Unlimited Fibre installed yesterday.
It's profiled at 40/10 at the moment rather than 80/20. Does anyone know if this will get fixed automatically, or do I need to chase it?
ICMP traces don't really work like this. Each hop pretty much shows the round-trip-time to/from your machine to that particular host. If you get decent ping responses from the destination host then in most cases any intermediate hops are irrelevant.
Routers have a habit of favouring the actual routing of traffic rather than attributing resource to responding to ICMP packets. That's why the first hop's so high. The 582n de-prioritises ICMP packets. If you were to run a UDP or TCP trace you wouldn't see that.
That's part of a know problem that was actually fixed this morning (ref: 74168). If you can provide me with your account username or a recent support ticket reference then I'll get it sorted for you.
Best regards,
I know that, but I'm interested if hes on interleave or fast-path, but without an unlocked modem, you can never tell, unless you are on infinty where the first hop is around 5ms.
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms home.gateway [192.168.1.254]
2 16 ms 22 ms 16 ms lo0-central10.ptn-ag04.plus.net [195.166.128.193
]
3 16 ms 15 ms 16 ms link3-central10.ptn-gw01.plus.net [84.93.248.228
]
4 16 ms 15 ms 15 ms xe-10-1-0.ptw-cr01.plus.net [212.159.1.44]
5 16 ms 15 ms 28 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
6 * * * Request timed out.
7 15 ms 16 ms 15 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 16 ms 19 ms 16 ms 132.185.255.60
9 17 ms 16 ms 16 ms 212.58.241.131
Trace complete.
So if the core network is congested and one user tries to torrent or use usenet..what speed might they expect? Below what threshold would Plusnet begin to take interest?
Looks like the first plusnet hop is in London (based on name, and latency on subsequent hops)...
2 21 ms 16 ms 16 ms lo0-central10.ptw-ag03.plus.net [195.166.128.197]
Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 5 ms 5 ms 5 ms 217.32.144.162
3 6 ms 6 ms 5 ms 217.32.144.206
4 7 ms 7 ms 7 ms 213.120.181.50
5 7 ms 7 ms 7 ms 217.41.169.207
6 7 ms 7 ms 7 ms 217.41.169.109
7 7 ms 7 ms 7 ms 109.159.251.211
8 16 ms 18 ms 12 ms core1-te0-12-0-6.ilford.ukcore.bt.net [109.159.
51.133]
9 15 ms 13 ms 12 ms peer2-xe11-0-0.telehouse.ukcore.bt.net [109.159
254.130]
10 13 ms 15 ms 14 ms 194.74.65.42
11 * * * Request timed out.
12 * * * Request timed out.
13 14 ms 14 ms 13 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
14 15 ms 14 ms 16 ms 132.185.255.148
15 12 ms 15 ms 15 ms bbc-vip115.telhc.bbc.co.uk [212.58.244.70]
Looks like the first plusnet hop is in London (based on name, and latency on subsequent hops), so it's hard to tell if it's 8ms of interleave in one direction (ie 12-13ms first hop) and 3-4ms of transit from the midlands to london
OR
no interleave, 3-4ms transit, and 7-8ms of BT mystery network shenanigans.
I would love it if it were the first, but probably the second.
Or he's not in the midlands at all and this piece of information is throwing me off!![]()
'ptw' is Telehouse West meaning the edge router bremen1874's connected to is based in one of our data suites down in London docklands.
I should have mentioned that those trace routes were from Nuneaton. According to a tool I came across I'm currently connected to ptw-ag03 in Telehouse West.
//edit ignore.... seems to be pricey everywhere.
What's the minimum contract on the fibre chaps ?
Ah I see. That's the hops across BT's 'Retail Internet Network'. You don't see the equivalent with a Plusnet connection.
A few years back we did have a number of customers provisioned on BT Retail's network as part of a trial. I saw similar traces from my connection back then.
Ultimately, whether fast-path or not, ISPs have little control over FTTx interleaving at present (hopefully that will change). With copper it's easy to turn on/off etc.
Best regards,
@MagicUK Have you emailed nga.enquiries@openreach.co.uk?