|
|
Also may be worth posting a tracert to the TBB one, just to confirm you are routing the same way, mine is:
Here's my traceroute. Not quite the same as yours.
| Text | 1
23
45
6 | traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 30 hops max, 38 byte packets
1 222.53.155.90.in-addr.arpa (90.155.53.222) 6.980 ms 6.878 ms 7.139 ms 2 q-aimless.tch.aa.net.uk (90.155.53.109) 7.266 ms 7.237 ms 7.416 ms
3 lonap-gw1.thdo.ncuk.net (5.57.80.142) 7.754 ms 7.562 ms 7.566 ms 4 po4-31.core-rs4.thdo.ncuk.net (80.249.97.85) 7.754 ms 11.235 ms 7.925 ms
5 pingbox1.thinkbroadband.com (80.249.99.164) 7.487 ms 7.779 ms 7.405 ms |
Adrian
|
|
|
Here's my traceroute. Not quite the same as yours.
| Text | 1
23
45
6 | traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 30 hops max, 38 byte packets
1 222.53.155.90.in-addr.arpa (90.155.53.222) 6.980 ms 6.878 ms 7.139 ms 2 q-aimless.tch.aa.net.uk (90.155.53.109) 7.266 ms 7.237 ms 7.416 ms
3 lonap-gw1.thdo.ncuk.net (5.57.80.142) 7.754 ms 7.562 ms 7.566 ms 4 po4-31.core-rs4.thdo.ncuk.net (80.249.97.85) 7.754 ms 11.235 ms 7.925 ms
5 pingbox1.thinkbroadband.com (80.249.99.164) 7.487 ms 7.779 ms 7.405 ms |
Looks to be the same route. Hop 1 is going to vary for most of us, its 3 and 4 that show the route to TBB and that is the same in terms of being the changed one.
I would certainly try a second opinion in the form of setting up another BQM from f8lure, and see if that is the same and take it from there. Are you having any noticeable issues with your connection?
It might be your router just doesn't prioritise pings or an issue on the line. What does your chart look like on the AA portal?
|
|
|
I have set up a test from f8lure, just letting it run for a day. AA pings look absolutely fine, speed tests are excellent, no issues with day to day internet use. Unlikely to be a router issue as TBB BQM with IDNet was fine too.
I can't say I am too bothered about it as everything seems to work OK and ultimately that's what matters.
Adrian
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
The latency is odd, it seems to be caused with the routing between TBB & AA - not the actual DSL service (ie, AA to customer). I see the spikes on my home line too with TBB graphs. I do have a suspicion as to what is causing this though, I'll investigate some more.
That did it, my graphs look great now. (in sig)
Edited by Chrysalis (Fri 17-Jun-22 14:56:05)
|
|
|
Interesting your IPv6 looks good as well as IPv4, which prompted me to check mine again, and IPv6 isn't showing any improvement except for some time over night for some reason.
https://www.thinkbroadband.com/broadband/monitoring/...
Route is:
| Text | 1
23
45
6 | <1 ms <1 ms <1 ms pfSense.localdomain [2001:8b0:----]
7 ms 7 ms 6 ms y.witless.thn.aa.net.uk [2001:8b0:0:53::134] 7 ms 7 ms 7 ms q-aimless.tch.aa.net.uk [2001:8b0:0:53::109]
8 ms 7 ms 7 ms ipv6.lonap-gw1.thdo.ncuk.net [2001:7f8:17::5394:1] 7 ms 7 ms 7 ms po4-31.core-rs4.thdo.ncuk.net [2a02:68:0:31::17]
7 ms 7 ms 7 ms ipv6.pingbox1.thinkbroadband.com [2a02:68:1::164] |
IPv4 has been good since the routing change Andrew mentioned here.
|
|
|
I had noticed a service status update for a new link https://aastatus.net/42436 not sure if it was related, guessing it is, as from today my IPv4 speed tests to TBB on the lonap route are looking great and no longer seem to hit a 350Mbps ceiling on the single thread tests.
https://www.thinkbroadband.com/speedtest/16561447523...
BQMs to TBB are still spiky compared to previous ISPs, especially IPv6, but better than it was.
IPv6
https://www.thinkbroadband.com/broadband/monitoring/...
IPv4
https://www.thinkbroadband.com/broadband/monitoring/...
Edited by E300 (Sat 25-Jun-22 09:28:04)
|
|
|
Well its not so good now, they changed the routing back on IPv6, and IPv4 also isnt as good on mine as it was when I last posted in this thread, I dont know if thats down to my usage or this issue though.
Edited by Chrysalis (Fri 01-Jul-22 15:59:43)
|
|
|
Post deleted by E300
Edited by E300 (Sat 02-Jul-22 13:46:38)
|
|
|
I'm seeing the same routing change. Also I'm noticing some packet loss (matching loses on TBB, f8lure and in my control panel), nothing excessive by any means, just now and again, but its gone from absolutely none to every day there is usually a little wobble. We've had on two occasions very recently the odd flicker of corruption when watching Amazon Prime on the TV, which is unusual, and looking at the charts on AAISP I can see drips of red at the time we would be watching.
I see on your chart a few packets lost at around 10pm last night, and I see exactly the same spots of red on mine. Something not quite right somewhere.
|
|
|
Just replying to my post regarding the noticed packet loss that has been ongoing for a few weeks on and off and I suggested something not right somewhere.
There was a period of heavier packet loss last night (July 4th) around the hour of 10 pm and this affected FTTP services it seems and down to congestion. These dropped packets do show on my BQMs and in the control panel but I wasn't doing anything on the net to notice. So it is known and fixes being worked on by AAISP. Quickly spotted, I know from other ISPs you can have these issues and nothing gets done for months!
https://aastatus.net/42441
Edited by E300 (Tue 05-Jul-22 16:59:38)
|
Pages in this thread: 
Print Thread
Adrian
