|
|
Might well be that, it does appear that from here to TBB goes via LONAP. Be interesting to see if it is a permanent change. I did have a scroll back through my TBB history and didn't see any similar duration improvement in the past, so hope it isn't just a transient. It's the only thing that had me (irrationally) slightly "jealous" of my old Zen link.
If it is that improvement at LONAP, it goes to show how careful you need to be if relying on any one given metric! Only as good as the weakest link.
traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 30 hops max, 46 byte packets
1 z.witless.thn.aa.net.uk (90.155.53.135) 7.874 ms 7.304 ms 7.858 ms
2 q-aimless.tch.aa.net.uk (90.155.53.109) 7.831 ms 6.894 ms 7.736 ms
3 lonap-gw1.thdo.ncuk.net (5.57.80.142) 8.025 ms 7.961 ms 7.759 ms
4 ae11-11.edge-rt5.thdo.ncuk.net (80.249.97.21) 7.745 ms 7.516 ms 7.845 ms
5 te1-51-36.core-rs3.thdo.ncuk.net (80.249.97.72) 8.063 ms 8.046 ms 7.648 ms
6 po5-32.core-rs4.thdo.ncuk.net (80.249.97.90) 7.863 ms 8.607 ms 7.696 ms
7 pingbox1.thinkbroadband.com (80.249.99.164) 7.608 ms 7.474 ms 7.852 ms
|
|
|
|
The Internet: Only as good as the weakest link. 👍
|
|
|
Hi, yep just came on to post a note about this, I had noticed the charts had cleaned up quite nicely and speedtests to TBB seem to be sustaining slightly higher levels so presumably part of the same change.
| Text | 1
23
45
67
89
1011
| Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1] 2 7 ms 7 ms 7 ms y.witless.thn.aa.net.uk [90.155.53.134]
3 7 ms 7 ms 7 ms q-aimless.tch.aa.net.uk [90.155.53.109] 4 8 ms 7 ms 7 ms lonap-gw1.thdo.ncuk.net [5.57.80.142]
5 7 ms 7 ms 7 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21] 6 8 ms 7 ms 7 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
7 8 ms 7 ms 7 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90] 8 7 ms 7 ms 7 ms pingbox1.thinkbroadband.com [80.249.99.164] |
Helps having a clean baseline to spot other issues in the future.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Just noticed on the BQM a step change for the better in my latency. Best I've seen until now is 6.7ms to AAISP, this is when I connect to y.witless, as per the previous trace route above. After AAISP did some shuffles a few weeks ago for an update I've been routing to x.witless, which was giving me around 7.6ms. x.witless always seems to add about a ms, I believe it is in a different location.
Anyway just seen my latency is now 5.5ms to x.witless, this changed about an hour or so ago, and my connection hadn't dropped in that time according to the router stats, and no dropped packets on the BQM, it just starts routing with lower latency. This improved latency is to all destinations, new trace route below. This is the lowest latency I have seen from my address ever.
Just wondering what might have happened, obviously I've not moved physically any closer to the first hop. Anyone else seen the same?
https://www.thinkbroadband.com/broadband/monitoring/...
| Text | 1
23
45
67
89
1011
| Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1] 2 5 ms 5 ms 5 ms x.witless.thn.aa.net.uk [90.155.53.133]
3 5 ms 6 ms 6 ms q-aimless.tch.aa.net.uk [90.155.53.109] 4 6 ms 6 ms 6 ms lonap-gw1.thdo.ncuk.net [5.57.80.142]
5 6 ms 8 ms 6 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21] 6 6 ms 6 ms 6 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
7 6 ms 6 ms 6 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90] 8 6 ms 6 ms 6 ms pingbox1.thinkbroadband.com [80.249.99.164] |
|
|
|
Just noticed on the BQM a step change for the better in my latency. Best I've seen until now is 6.7ms to AAISP, this is when I connect to y.witless, as per the previous trace route above. After AAISP did some shuffles a few weeks ago for an update I've been routing to x.witless, which was giving me around 7.6ms. x.witless always seems to add about a ms, I believe it is in a different location.
I doubt it is an improvement at AAISP, as anything yielding such a large improvement would imply something quite wrong going on previous. As far as I can tell now all the significant latency is coming from BTW's core network and is hidden to us in the first hop, so I'd imagine something changed within that network. I didn't see any step change, though I am on y.witless at the moment.
I have an old BQM running against z.witless and the background latency level is always almost non-existent:
My Broadband Ping
My latency into AAISP however is significantly higher than Zen's own network was. I think Zen tended to have more direct routes whereas BTW goes through many more devices. I'm not complaining though, as the AAISP service is much better than Zen's.
|
|
|
The latency jumped back again so it didn't last, again no disconnect or any lost packets as the route changed, yes I agree, I suspect something BTW have been doing and I got routed more directly for some reason.
So pfSense dashboard was showing 5.6ms to the gateway for a while, now back to 7.5ms. Obviously it isn't noticeable using the connection, but 5.6ms looks a looks better 
|
|
|
Just adding to this some time later, we seem to be back via Linx again, the change appeared around 1pm yesterday (14 June 2023) and the same spiky looking BQMs are back, not too bad on IPv4 but IPv6 looks bumpy. Perhaps just a temporary change due to a problem elsewhere.
| Text | 1
23
45
67
8 | 1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 7 ms 7 ms 7 ms x.witless.thn.aa.net.uk [90.155.53.133]3 7 ms 7 ms 7 ms k-aimless.thn.aa.net.uk [90.155.53.101]
4 8 ms 8 ms 8 ms linx-gw1.thn.ncuk.net [195.66.224.240]5 8 ms 8 ms 8 ms ae11-11.edge-rt2.thdo.ncuk.net [80.249.97.21]
6 8 ms 8 ms 8 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]7 8 ms 8 ms 8 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90]
8 8 ms 8 ms 8 ms pingbox1.thinkbroadband.com [80.249.99.164] |
Edited by E300 (Thu 15-Jun-23 15:19:48)
|
|
|
Hrmm... these look quite a bit worse than they used to for me pre-change at BQM towers...
This is the changeover:
My Broadband Ping
Might be worth mentioning to @seb ?
|
|
|
Just adding to this some time later, we seem to be back via Linx again, the change appeared around 1pm yesterday (14 June 2023) and the same spiky looking BQMs are back, not too bad on IPv4 but IPv6 looks bumpy. Perhaps just a temporary change due to a problem elsewhere.
| Text | 1
23
45
67
8 | 1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 7 ms 7 ms 7 ms x.witless.thn.aa.net.uk [90.155.53.133]3 7 ms 7 ms 7 ms k-aimless.thn.aa.net.uk [90.155.53.101]
4 8 ms 8 ms 8 ms linx-gw1.thn.ncuk.net [195.66.224.240]5 8 ms 8 ms 8 ms ae11-11.edge-rt2.thdo.ncuk.net [80.249.97.21]
6 8 ms 8 ms 8 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]7 8 ms 8 ms 8 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90]
8 8 ms 8 ms 8 ms pingbox1.thinkbroadband.com [80.249.99.164] |
Yes, we re-enabled our LINX session to NetConnex who host the BQM hardware - though, I'm not really sure why it makes such a difference as neither us or NetConnex see a problem on LINX generally!
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
Thanks Adrian for your reply. I don't know what else I might use that takes the same route (if anything does), so it doesn't seem to affect anything here either except for a rough looking BQM, although I can see IPv6 has now returned to being quite flat again and can see this is routing via lonap-gw1.
|
Pages in this thread: 
Print Thread
jimbof
andrewhearn