|
|
Normal on Pulse8 (using TTB) i get a regular 36-38ms ping interleaving on. Noticed tonight that has jumped to 42-44ms for no reason. Speed tests are fine both download and upload so i know nothing is trying to use the connection (tested anyway by removing as many devices as possible from it).
1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 28 ms 29 ms 88-104-176-1.dynamic.dsl.as9105.com [88.104.176.1]
3 29 ms 30 ms 29 ms 85-210-255-110.dynamic.dsl.as9105.com [85.210.255.110]
4 30 ms 29 ms 31 ms 85-210-252-19.dynamic.dsl.as9105.com [85.210.252.19]
5 36 ms 35 ms 35 ms host-78-144-10-39.as13285.net [78.144.10.39]
6 61 ms 35 ms 35 ms xe-1-1-0.r2.bb-fo.lon3.vrsn.net [195.66.225.46]
7 67 ms 51 ms 36 ms xe-0-2-0.r1.bb-fo.lon3.vrsn.net [199.16.94.153]
8 41 ms 43 ms 43 ms xe-4-3-0.r1.bb-fo.ams1.vrsn.net [199.7.62.20]
9 43 ms 43 ms 43 ms ae2.666.r1.vidn-fo.ams1.vrsn.net [199.16.95.153]
10 42 ms 42 ms 42 ms 199.16.80.66
11 44 ms 44 ms 43 ms 217.30.83.10
12 45 ms 45 ms 45 ms 132.185.255.149
13 44 ms 44 ms 44 ms
C:\Users\User>tracert google.co.uk
Tracing route to google.co.uk [74.125.71.94]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 28 ms 28 ms 88-104-176-1.dynamic.dsl.as9105.com [88.104.176.1]
3 30 ms 29 ms 29 ms 85-210-255-110.dynamic.dsl.as9105.com [85.210.255.110]
4 29 ms 30 ms 29 ms 85-210-255-71.dynamic.dsl.as9105.com [85.210.255.71]
5 36 ms 35 ms 35 ms host-78-144-8-45.as13285.net [78.144.8.45]
6 35 ms 35 ms 35 ms 72.14.214.222
7 36 ms 36 ms 36 ms 209.85.252.188
8 36 ms 37 ms 37 ms 209.85.143.67
9 44 ms 43 ms 43 ms 216.239.41.236
10 42 ms 43 ms 42 ms 216.239.51.211
11 * * * Request timed out.
12 41 ms 42 ms 41 ms wn-in-f94.1e100.net [74.125.71.94]
Not sure why pings will have gone up alittle for no reason although doesnt seem to be from within TT
Edited by bobble_bob (Tue 01-Dec-15 21:16:33)
|
|
|
FTTC or ADSL2+?
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59997/15142kbps @ 600m. - BQM
|
|
|
|
ADSL 2+ no disconnects at all. Weirdly the thinkbroadband BQM (ive only just set it off running) shows normal pings, as do all pingtest websites. Just seems its command prompt that is showing higher than normal
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Looks like nothing to do with the local broadband connection but something from hop 7 and hop 9 in the trace routes
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Could be just some routes to sites on the Internet are affected
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
Are 7-9 outside of the Talk talk network can you tell?
|
|
|
http://whois.domaintools.com/209.85.252.188
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59997/15142kbps @ 600m. - BQM
|
|
|
Yes they are... and it goes from London to Amsterdam hence the increase in latency on that route specifically.
Matt
|
|
|
|
I use openDNS and notice they did some work today on the London server, although its cleared now but wonder if that could be a reason as i would be redirected to a DNS server overseas
|
|
|
Might not be advertising the route to all their peers in London/UK... or that route may be the best for Talk Talk (as far as BGP is concerned).
Matt
|
|
|
|
I assume if it is a opendns rerouting thing, that eventually i will be back on the London server?
Pretty sure when ive done traceroutes to bbc before it hasnt gone to "ams1.vrsn.net" where the problem seems to be
|
|
|
Those two tracerts have essentially the same latency. (2ms difference). A high point in the middle of one indicates a router that is giving pings a low priority compared to data packets.
It's a high that then maintains the height for subsequent hops that points to a slow/congested router.
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59997/15142kbps @ 600m. - BQM
Edited by RobertoS (Tue 01-Dec-15 21:52:50)
|
|
|
BBC will have completely different routes generally, probably via private peering or over Linx or similar due to massive amounts of traffic. I can't tell as I don't have access to a native TT connection.
It may go back to the UK but it is controlled by OpenDNS mainly and to a lesser extent Talk Talk but either can influence traffic as they see fit.
Matt
Edited by uno (Tue 01-Dec-15 21:53:29)
|
|
|
|
Is there any pingtest that tests using data packets, rather than ICMP to give a more accurate result if a router is giving low priority to pings?
Although maybe the BMQ does this hence the pings are fine
|
|
|
BQM is ICMP echo
Probably not affected as the ping box is in a data centre in London
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Ah thanks. Strange my traceroute of the bbc goes through a server in London, then to Amsterdam then back to BBC HQ is London again. Seems a long way around
Edit: Seems it must be some routing issue as google pings are back to normal. BBC still high but probably that pesky Amsterdam server
Edited by bobble_bob (Tue 01-Dec-15 23:26:51)
|
Pages in this thread: 
Print Thread
bobble_bob
