Spending too much time talking to 1st level support who can't help. I need technical assistance with routing that just dies.
These outages are happening more frequently and range from 30mins to 2hrs. Connection recovers but repeats. Similar results with netflix facebook, youtube etc
BBC consistently fails at 78.144.1.34
Can any one help please?
eg Tue 21 Jan 22:12:48 GMT 2020
d@d-Latitude-E7450:~$ traceroute bbc.co.uk
traceroute to bbc.co.uk (151.101.192.81), 64 hops max
1 192.168.1.1 0.973ms 0.707ms 1.337ms
2 * 89.241.160.1 295.119ms *
3 78.144.1.35 3365.091ms * 348.325ms
4 * 78.144.1.34 783.824ms *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
Hi wetshoestring,
Can you please update your community profile to include your:
We'll then look into this further. Please do not post this information on this thread Once you've updated your profile please post in your topic to confirm it's updated.
Thanks
You really do need to complete your profile as the OCE has asked, only the OCE,s and you can see your details, if you want comprehensive support on your problem. When you have filled in the various section remember to scroll down and click the save button.
No problem glad to be of help.
Hi wetshoestring
Thanks for updating your Community Profile.
I've checked the connection stats and I can see that the SNR is dropping low and this can affect the performance of the connection.
I have optimised the connection and the SNR has increased. Please let us know how the connection compares following this.
Thanks
Debbie
Debbie,
Thanks for the update. Yip I saw the connection drop about 10.30, WFH today so particularly sensitive to changes. Back at a slightly higher connect speed (thanks for that!) traceroute is more responsive than it was earlier. Ookla is not finding test servers particualrly well however I recognise that is beyond your control and may or may not be related and could easily be an issue at their end.
It may be wise to cancel engineer visit on Thursday but I'd like to see how it goes for a couple of days? I do realise my line is marginal but Talktalk do seem to squeeze the best out of it.
Thanks for your help. I will go to forum first next time briiliant service!
Cheers,
Wetshoestring
Hi wetshoestring
Thanks for your reply.
Would you like to monitor the connection for 24hrs before cancelling the engineer visit?
Debbie
Debbie,
Hah! switch speed checker to talktalk, I see you use ookla too and it won't connect. Nor other speed checkers, having said that traceroute still good and connection responsive otherwise. Speedcheck does connect (eventually) and showning quite an improvement, Ookla still not answering via talktalk .
Would suggest any other checks?
I'll keep an eye over the next couple of days.
Thanks again.
Wetshoestring
Hi wetshoestring
Your line is showing in sync at just under 7mb.
Please let us know tomorrow how the connection has been today/tonight.
Thanks
Debbie
Hello Debbie,
Thanks for your help so far
Line seems ok but I still can't reach ookla test servers across all browsers and on different laptops, when I could before. This is a change in behaviour since the line tweaks. I'll just leave the engineer call jic this actually is a line issue after all.
Thanks in advance.
wetshoestring
Debbie,
Of course having just said that now traceroute is tanking again.
7.10 ok but speedcheck sites not available
7.30 I can't even load bbc and traceroute to google is taking a lonnng time. see traceroute below.
This looks increasingly like a contention issue to me. Have a look at this thread looks very similar:
d@d-Latitude-E7450:~$ traceroute www.google.co.uk
traceroute to www.google.co.uk (216.58.198.163), 64 hops max
1 192.168.1.1 1.893ms 2.744ms 1.996ms
2 89.241.160.1 2528.040ms 2574.105ms 2496.031ms
3 78.144.1.35 2498.871ms 2279.375ms 2355.448ms
4 78.144.1.34 1843.439ms 2457.684ms 2457.997ms
5 78.144.9.11 2253.780ms 2160.111ms 2248.530ms
6 72.14.208.22 2398.807ms 2061.651ms 2406.351ms
7 * * *
8 216.239.58.220 2451.834ms 2152.317ms 1841.501ms
9 74.125.242.82 2252.899ms 2128.640ms 1533.785ms
10 216.58.198.163 1566.900ms 1120.447ms 1315.879ms
d@d-Latitude-E7450:~$ traceroute www.google.co.uk
traceroute to www.google.co.uk (216.58.198.163), 64 hops max
1 192.168.1.1 0.936ms 0.727ms 0.655ms
2 89.241.160.1 2024.690ms 2149.928ms 1843.363ms
3 78.144.1.35 2150.672ms 2048.093ms 1843.256ms
4 78.144.1.34 1945.717ms 2458.448ms 1335.614ms
5 78.144.9.11 1019.135ms 1433.715ms 1438.503ms
6 78.144.4.35 1247.996ms 1102.466ms 1228.861ms
7 * * *
8 108.170.232.99 1151.016ms 1193.580ms 1237.635ms
9 74.125.242.83 1126.513ms 1023.876ms 1228.662ms
10 216.58.198.163 1412.092ms 1865.238ms 2744.068ms
Debbie,
Apologies lost the ref! Here it is:
It looks like large chunks of talktalk backbone disappear...
Thanks.
Debbie
...and its back
traceroute now reporting
2 89.241.160.1 72.778ms 75.473ms 76.117ms
when 15mins ago it was saying
2 89.241.160.1 2981.909ms 2209.903ms 2067.306ms
lets see what the engineer says.
Thanks.
Hi wetshoestring,
Thanks for the information, please let us know how the engineer visit goes tomorrow
Chris
Chris, Community Team
Our latest Blog l Share your Ideas l Service Status l Help with your Service l Community Stars l Set your preferences
Hello,
TT engineer prompt and very nice, deserved his cup of tea. Checked out the wiring and connection which of course was working just fine when he checked. Reckons as I do we're getting the best we can out of the line. BUT agreed the traceroute stats look pants when they are bad but no obvious physical hardware issues between the router and the exchange.
This leaves the trunk and back bone capacity. It reeks of load balancers not coping and fail overs not failing over but hey it's not my network it's TT's. Line stays up and connected fine (stats back that) it's the routing that falls over traffic just stops or is severely delayed inbetween hops. This looks deep in TT (openreach?) nw.
Having said that no issues since a couple of days ago, will continue to monitor.
Thanks
Hi wetshoestring,
Thanks for keeping us updated and please let us know how the connection compares over the weekend 🙂
Thanks
Hello,
Connectrion largely behaing itself but resolutely does not connect to ookla either via web or directly using cli widget: xx's are to cover ip
using vanila config:
d@d-Latitude-E7450:~/Downloads/ookla-speedtest-1.0.0-x86_64-linux$ speedtest-cli
Retrieving speedtest.net configuration...
Testing from TalkTalk (xx.xxx.xxx.xx)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Odyssey Systems Limited (Stockton On Tees) [196.93 km]: 1800000.0 ms
Testing download speed................................................................................
Download: 0.00 Mbit/s
Testing upload speed......................................................................................................
Upload: 0.00 Mbit/s
Using specific test server:
Retrieving speedtest.net configuration...
Testing from TalkTalk (xx.xxx.xxx.xx)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Wildcard Networks (Newcastle upon Tyne) [150.60 km]: 1800000.0 ms
Testing download speed................................................................................
Download: 0.00 Mbit/s
Testing upload speed......................................................................................................
Upload: 0.00 Mbit/s
This is consistent with web ie thepings just time out and so does the connection.
Ideas?
Thanks in advance
Hello,
Bah! connection showing dodgy trace routes again which spontaneously recover:
d@d-Latitude-E7450:~$ traceroute www.google.co.uk
traceroute to www.google.co.uk (216.58.210.35), 64 hops max
1 * 192.168.1.1 0.701ms 0.735ms
2 * 89.241.160.1 243.650ms *
3 78.144.1.35 2564.819ms 2454.278ms 2895.976ms
4 * 78.144.1.34 406.504ms 2132.840ms
5 78.144.9.27 1682.437ms 1421.857ms 1235.758ms
6 78.144.4.35 37.626ms 37.681ms 35.939ms
7 108.170.246.129 45.488ms 74.221ms 36.156ms
8 216.58.210.35 36.223ms 46.246ms 35.920ms
d@d-Latitude-E7450:~$ traceroute www.google.co.uk
traceroute to www.google.co.uk (216.58.210.35), 64 hops max
1 192.168.1.1 1.155ms 0.809ms 0.770ms
2 89.241.160.1 24.604ms 24.125ms 25.458ms
3 78.144.1.35 29.408ms 29.711ms 29.100ms
4 78.144.1.34 29.343ms 30.139ms 29.712ms
5 78.144.9.11 36.523ms 36.105ms 36.724ms
6 72.14.208.22 35.349ms 36.279ms 35.795ms
7 * * *
8 108.170.232.105 35.300ms 35.613ms 34.723ms
9 216.58.210.35 36.100ms 35.342ms 36.322ms
I'd say problem remains. Interestingly enough other test sites work just fine. Ookla consistently fails to load now when it was formerly my go to test site. Any luck with finding an underlying nw issue?
Ta
wetshoesting