cancel
Showing results for 
Show  only  | would you rather see results for 
Did you mean: 
Need help?

connection stable but periodically sites not reachable bbc netflix facebook etc

Reply
Highlighted
Team Player

Woa!

 

Summit happening at the exchange end again this morning. Thanks for grinding away at the problem TT!

 

Ta,

 

wetshoestring

Highlighted
Community Team - TT Staff

Hi wetshoestring,

 

Apologies, this will be due to the line test which I've just completed on the line. I've run the test as I can see an increase in errored seconds which can affect the performance of the connection, however the line test is clear.

 

Is the voice service ok with no noise on the line? Does your master socket have a test socket? If it does then would it be possible to connect the router at the test socket to see if the errored seconds reduce? Have you also tested with a different router before?

 

Thanks

 

Highlighted
Team Player

hello,

 

..er? we swept that all up with a site visit last week with the TT engineer? Line quiet, wiring to master good, using built in filter on the master socket. I think we maybe continuing to bark up the wrong tree here?

 

As I understand traceroute is showing delays between hops way down the nw chain not between the internal router and the first hop . The bband router is supplied by talktalk (their latest and greatest and to the latest firmware) this was also checked by the TT engineer when he was on site and passed as good. 

 

I really think having looked at the internal wiring, equipment and configuration we can discount my internals. Correct me if I'm wrong but that's what the TT engineer visit was for?  Although I do appreciate you are trying to help.

 

The weird one to me is the consistent refusal of ookla to work on any web browser, on any platform (incluing the cli version) when adroid ookla tests DO work. That and the inconsistent traceroute stats far down the chain make me think TT or probably more accurately BT nw is at fault. Given what I've just described and the recent site visit by TT why do you think it is still my internals at fault and not the NW? What explanation do you have for delayed hops that are far down the chain?

 

Thanks in advance.

 

wetshoestring

Highlighted
Community Team - TT Staff

Hi wetshoestring,

 

Ok, could you run another wired ping and trace route the next time you experience this issue please and we can ask our Network Team to take a look to see if they can see/find any issues. Are social sites also still affected and intermittently not loading as well as the speed tester site?

 

In regards to the internal set up question, as we can see an increase in errored seconds I just wanted to see if the performance issues you're experiencing may be related to the increase in errored seconds on the line.

 

Thanks

 

Highlighted
Team Player

hello,

 

gone sluggish again at 23.10 04/02/2020 til about 23.20

 

Stats below. But to answer your question ookla NEVER reaches a server now no matter if the traceroute is good or bad. BUT if I use android via phone I do reach ookla. Unfortunately (fortunately?) traceroute recovered. after about 10 minutes all good now.

 

Performing some more specific tests which I'll report in another entry. Telnet'ing to ookla to see if it answers on the port as expexcted. I think a port is being blocked..

 

 

ping ok:

 

d@d-Latitude-E7450:~$ ping www.google.co.uk
PING www.google.co.uk (172.217.169.67) 56(84) bytes of data.
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=1 ttl=54 time=52.6 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=2 ttl=54 time=43.9 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=3 ttl=54 time=51.2 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=4 ttl=54 time=49.8 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=5 ttl=54 time=63.9 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=6 ttl=54 time=45.2 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=7 ttl=54 time=46.0 ms
64 bytes from lhr48s09-in-f3.1e100.net (172.217.169.67): icmp_seq=8 ttl=54 time=44.6 ms
<snip>

 

but traceroute pants:

 

raceroute to www.google.co.uk (216.58.204.3), 64 hops max
 1   *  192.168.1.1  1.929ms  0.955ms  
 2   *  89.241.160.1  1157.403ms  *  
 3   *  78.144.1.35  2528.164ms  *  
 4   *  78.144.1.34  683.905ms  *  
 5   78.144.9.27  3845.145ms  2583.837ms  *  
 6   *  72.14.208.22  376.331ms  *                                                                                                                                           
 7   *  74.125.242.97  49.689ms  *                                                                                                                                           
 8   172.253.68.218  2799.043ms  *  454.907ms                                                                                                                                
 9   *  108.170.246.176  1299.509ms  2867.697ms                                                                                                                              
10   216.58.204.3  3174.955ms  *  275.862ms                                                                                                                                  
d@d-Latitude-E7450:~/Downloads/ookla-speedtest-1.0.0-x86_64-linux$ traceroute www.google.co.uk                                                                                
traceroute to www.google.co.uk (216.58.204.3), 64 hops max                                                                                                                    
 1   192.168.1.1  1.747ms  0.874ms  0.792ms                                                                                                                                  
 2   *  89.241.160.1  550.368ms  2582.457ms                                                                                                                                  
 3   78.144.1.35  2640.700ms  2969.663ms  *                                                                                                                                  
 4   *  78.144.1.34  174.310ms  *  
 5   78.144.9.11  3962.003ms  2355.373ms  *  
 6   *  72.14.208.22  991.013ms  2457.818ms  
 7   *  74.125.242.97  479.089ms  *  
 8   *  64.233.175.91  273.978ms  *  
 9   108.170.246.175  3244.316ms  2969.813ms  *  
10   *  216.239.58.3  481.457ms  *  
11   216.58.204.3  4166.244ms  *  80.504ms  
d@d-Latitude-E7450:~/Downloads/ookla-speedtest-1.0.0-x86_64-linux$ traceroute www.google.co.uk
traceroute to www.google.co.uk (172.217.169.67), 64 hops max
 1   192.168.1.1  1.015ms  0.873ms  1.050ms  
 2   *  89.241.160.1  738.137ms  2511.611ms  
 3   78.144.1.35  2764.975ms  *  280.874ms  
 4   *  78.144.1.34  381.155ms  *  
 5   78.144.9.9  3132.555ms  2805.291ms  2929.529ms  
 6   *  78.144.4.35  634.758ms  2700.278ms  
 7   74.125.242.97  2472.331ms  *  2119.643ms  
 8   209.85.241.94  2133.494ms  1932.009ms  1392.424ms  
 9   108.170.246.176  1361.034ms  1409.351ms  1281.363ms  
10   172.217.169.67  1345.481ms  1457.085ms  1514.964ms

 

Highlighted
Team Player

Hi,

 

Here we go first check if I can reach ookla via cli application:

Nope.. and do remember trace route is good ATM

 

speedtest-cli --server 4058
Retrieving speedtest.net configuration...
Testing from TalkTalk (xx.xx.xx.xxx)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Wildcard Networks (Newcastle upon Tyne) [139.26 km]: 1800000.0 ms
Testing download speed................................................................................
Download: 0.00 Mbit/s
Testing upload speed......................................................................................................
Upload: 0.00 Mbit/s

IP address for Wildcard Networks 

 

ping speedtest.wildcard.net.uk
PING speedtest.wildcard.net.uk (31.22.2.67) 56(84) bytes of data.
64 bytes from speedtest.wildcard.net.uk (31.22.2.67): icmp_seq=1 ttl=56 time=86.7 ms
64 bytes from speedtest.wildcard.net.uk (31.22.2.67): icmp_seq=2 ttl=56 time=79.0 ms
64 bytes from speedtest.wildcard.net.uk (31.22.2.67): icmp_seq=3 ttl=56 time=39.3 ms

ok ping works but if I try telnet'ing the test port 8080, nada, no reply:

 

telnet 31.22.2.67 8080              
Trying 31.22.2.67...
telnet: Unable to connect to remote host: Connection timed out

 

I don't expect to get in but I do expect a response from the host as I get from google when I try the same thing:

 

d@d-Latitude-E7450:$ telnet 172.217.169.67 80
Trying 172.217.169.67...
Connected to 172.217.169.67.

Google replies, speedtest.wildcard.net does not which is why I can't connect to ookla via web app or cli app on a PC.

 

Does anyone know what is going on in TT's nw?

 

Disnae look right to me but hey! TT nw techs over to you what would you suggest I try to test this further? 

 

What do you think of what I've tested so far:

 

1 not reaching ookla (everytime I try (good or bad traceroute) - my test tenet test server on test port 8080

2 periodic no replies from web requests to common major providers, bbc, netfix,facebook, google - my test traceroute google when it's bad can't connect to web sites  (with no noise on line)

 

?

 

Thanks

 

Wetshoelace 

Highlighted
Team Player
Team Player

Hi,

 

Oops.. empty post. This was what I meant to say:

 

checking port 8080 it says:

 

 @d-Latitude-E7450:~$ nmap -p 8080 31.22.2.67

Starting Nmap 7.60 ( https://nmap.org ) at 2020-02-05 00:21 GMT
Nmap scan report for speedtest.wildcard.net.uk (31.22.2.67)
Host is up (0.040s latency).

PORT     STATE    SERVICE
8080/tcp filtered http-proxy

Nmap done: 1 IP address (1 host up) scanned in 0.48 seconds

'filtered' ie BLOCKED by firewall I don't run a firewall beyond stateful on the router  ie I can connect out to anything I want but only initiated replies are allowed.

 

Is TT blocking port 8080 on my connection?

 

This is an aside but maybe shows weird stuff happens on TT network..

 

Ta, wetshoestring 

 

Highlighted
Community Team - TT Staff

Hi wetshoestring,

 

Just before I pass this over could I clarify some information below,

 

This is currently intermittently affecting some social sites as well (won't load pages) on 2 different devices, including a wired device?

You've said that you can't connect to ookla but it works on your phone. Was your phone connected to wifi or data when it worked?

Have you made any specific changes to any router settings?

Have you ever tested with a different make and model of router? (if not then we can send one for testing to see how the connection compares and to rule this out)

 

Apologies for all the questions but I just want to ensure that we have all the correct information.

 

Finally one last thing, I've just re-read back through your thread and noticed that when we originally optimised the connection and the SNR increased then the connection seemed to have improved for a few days. I've tried this again now as the SNR does seem to be dropping a bit low at times to see if this does improve the performance again. If it does then this may be related to the SNR dropping too low and we can speak to our Network Team about this.

 

Thanks

 

Highlighted
Team Player

hi,

 

Thanks for continuing to chat about this, This keeping me up nights.. but good to brush up on my network tools! To answer your questions

 

<This is currently intermittently affecting some social sites as well (won't load pages) on 2 different devices, including a wired device?>

 

When traceroute goes bad it affects any web site. social, web, streaming, whatever, sometimes its so bad the browser (firefox,chrome,brave I've tried them all) times out and I get 'unreachable' or in the case of this site, TT community, it wouldn't authenticate in time to allow me to post. The bad traceroutes occur on wireless or wired, the web time outs occur on wireless or wired too ie issue is independent of local connection method but is consistent with bad traceroute.

 

<You've said that you can't connect to ookla but it works on your phone. Was your phone connected to wifi or data when it worked?>

 

Phone was connected to local wireless (NOT 4g), this was this same connection method TT engineer used on android tablet. I think android app uses different port number but this is speculation and can't test coz I don't know!

 

<Have you made any specific changes to any router settings?> 

 

Only the stafeful firewall tweak. I just turned this off and gues what ookla now answers! My bad my apologies for confusing the issue looks like I was blocking my own speed test to ookla. Thats embarressing. Scratch ookla unreachable complaint. For info firewall  low + med ok high stops ookla.

The only changes default wireless ID + password, TT engineer checked current router settings and ok'd them (including firewall). He did change the connection name for bband to phone  number it was at 01warehouse previously (as i recall). 

 

<Have you ever tested with a different make and model of router? (if not then we can send one for testing to see how the connection compares and to rule this out)> 

Nope. If you could send one I'll give it a bash, thanks!

 

Well that helps! Thanks for prodding away looks like we've only got the slow intermittent (yay!) traceroute issue. Well thats ok then... 🙂

Thanks again.

 

 

 

Highlighted
Community Team - TT Staff

Hi wetshoestring,

 

Thank you. Would it be possible to test this throughout today (if you get a chance) to see how the performance now compares since I optimised the connection this morning? Would you like us to send the same router or try a HG633 router instead?

 

Thanks

 

Highlighted
Team Player

Hello,

 

My next chance to test through the day is Saturday and I'll give it go.

 

In answer to your alternate router lets go with the same type ie latest sagem based unit. Then we'll be comparing like with like.

 

traceroute is lacklustre ATM 21.30 06/02/2020

 

 d@d-Latitude-E7450:~/Downloads/ookla-speedtest-1.0.0-x86_64-linux$ traceroute www.google.co.uk
traceroute to www.google.co.uk (216.58.210.35), 64 hops max
 1   192.168.1.1  0.787ms  0.653ms  1.515ms  
 2   89.241.160.1  257.892ms  297.323ms  298.656ms  
 3   78.144.1.35  368.310ms  125.421ms  149.601ms  
 4   78.144.1.34  138.547ms  140.760ms  131.821ms  
 5   78.144.9.9  96.131ms  198.171ms  84.146ms  
 6   72.14.208.22  87.968ms  101.418ms  125.962ms  
 7   108.170.246.161  115.673ms  121.048ms  123.603ms  
 8   108.170.232.105  126.186ms  130.475ms  127.985ms  
 9   108.170.232.103  131.654ms  133.243ms  154.703ms  
10   216.58.210.35  142.395ms  172.082ms  121.527ms

 

now fine:

 

traceroute to www.google.co.uk (216.58.204.3), 64 hops max
 1   192.168.1.1  0.658ms  0.787ms  0.626ms  
 2   89.241.160.1  23.098ms  24.147ms  23.211ms  
 3   78.144.1.35  28.808ms  29.549ms  29.303ms  
 4   78.144.1.34  29.074ms  28.545ms  29.116ms  
 5   78.144.9.7  37.560ms  37.773ms  35.618ms  
 6   78.144.4.35  35.591ms  34.845ms  35.029ms  
 7   74.125.242.97  38.787ms  39.094ms  38.159ms  
 8   172.253.66.86  37.788ms  37.141ms  37.562ms  
 9   216.58.204.3  36.707ms  36.401ms  36.836ms

?

 

Thanks for your continuing help.

Highlighted
Community Team - TT Staff

Hi wetshoestring

 

The replacement WiFi Hub is on its way, please allow 24-48hrs for this to arrive.

 

Let us know how the connection compares with this router.

 

Thanks

 

Debbie