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

Erratic download speed and ping

Reply
8 REPLIES 8
Highlighted
Chat Champion

I recently logged an issue via online chat regarding my Faster Fibre service wich had sudenly lost half of its line sync speed. After some tests an Openreach engineer visited and replaced my master socket, drop line crimps and switched lines in both the street cabinet and local exchange. The result was that sync speed was imprtoved to better than it had been previously and max throughput was improved however the connection is erratic, ping varies from 6ms to over 150ms without any load on the line and download speed varies from 1MBPS to 50+MBPS. At all time the connection quality seems degraged as voice over IP and video calls etc are very low quality and sometimes impossinble even when download speed are showing a being high.

Highlighted
Community Team - TT Staff

Hi Doodah,

 

I'm sorry to hear this. I've run a test on the line which hasn't detected a fault. Just to confirm, does this also happen if you connect wired?

 

Thanks

 

Highlighted
Chat Champion

Hi Michelle,

Yes it does happen with wired connection as well. It is getting worse, today every few minutes ping goes really high and throughput drops really low, I am totally unable to work. BTW, previously I said I had Faster Fibre, I actually have Superfast.

Highlighted
Community Team - TT Staff

Hi Doodah,

 

Thanks for confirming. Does it happen at a certain time of the day (of an evening) or at any time? Please can you run a wired ping and trace route and post the results into the thread.

 

Run a Ping or Traceroute

 

Thanks

 

Highlighted
Chat Champion

Hi Michelle,

 

The erratic download speed issue has continued but it has been difficult to get the tests done at the correct moment due to work commitments, however I have managed to do it today. Results of ping and traceroute below. BTW, I am a Linux user so the output may be slightly different to what you are used to.

 

$ ping www.google.co.uk
PING www.google.co.uk (142.250.27.94) 56(84) bytes of data.
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=1 ttl=105 time=29.9 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=2 ttl=105 time=29.3 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=3 ttl=105 time=29.2 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=4 ttl=105 time=29.6 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=5 ttl=105 time=29.8 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=6 ttl=105 time=29.4 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=7 ttl=105 time=31.1 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=8 ttl=105 time=29.0 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=9 ttl=105 time=31.2 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=10 ttl=105 time=29.5 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=11 ttl=105 time=29.3 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=12 ttl=105 time=30.1 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=13 ttl=105 time=29.6 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=14 ttl=105 time=29.3 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=15 ttl=105 time=29.1 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=16 ttl=105 time=29.3 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=17 ttl=105 time=29.5 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=18 ttl=105 time=29.0 ms
^C64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=19 ttl=105 time=29.0 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=20 ttl=105 time=29.1 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=21 ttl=105 time=28.9 ms
64 bytes from 142.250.27.94 (142.250.27.94): icmp_seq=22 ttl=105 time=29.6 ms
^C
--- www.google.co.uk ping statistics ---
22 packets transmitted, 22 received, 0% packet loss, time 42ms
rtt min/avg/max/mdev = 28.923/29.540/31.181/0.626 ms

 

=======================================================================

 

$ traceroute www.google.co.uk
traceroute to www.google.co.uk (142.250.27.94), 30 hops max, 60 byte packets
1 _gateway (192.168.50.1) 14.634 ms 14.538 ms 14.449 ms
2 192.168.1.254 (192.168.1.254) 14.372 ms 14.244 ms 16.677 ms
3 ae50-ner001.thw.as13285.net (78.144.1.1) 21.461 ms 21.332 ms 21.346 ms
4 ae50-scr101.thw.as13285.net (78.144.1.0) 23.108 ms 23.085 ms 21.133 ms
5 72.14.209.10 (72.14.209.10) 22.986 ms 22.912 ms 26.869 ms
6 10.252.56.158 (10.252.56.158) 26.919 ms 10.252.231.126 (10.252.231.126) 24.757 ms 10.252.36.126 (10.252.36.126) 22.713 ms
7 172.253.66.98 (172.253.66.98) 22.542 ms 74.125.242.97 (74.125.242.97) 24.395 ms 24.306 ms
8 108.170.246.143 (108.170.246.143) 23.526 ms 74.125.242.82 (74.125.242.82) 46.260 ms 46.193 ms
9 216.239.58.129 (216.239.58.129) 23.106 ms 216.239.58.131 (216.239.58.131) 24.759 ms 209.85.250.185 (209.85.250.185) 24.596 ms
10 209.85.245.230 (209.85.245.230) 30.061 ms 209.85.142.166 (209.85.142.166) 29.959 ms 209.85.245.230 (209.85.245.230) 29.800 ms
11 142.250.59.215 (142.250.59.215) 31.743 ms 142.250.59.189 (142.250.59.189) 29.604 ms 142.250.59.191 (142.250.59.191) 347.066 ms
12 216.239.63.95 (216.239.63.95) 345.857 ms 108.170.233.125 (108.170.233.125) 345.840 ms 209.85.251.225 (209.85.251.225) 345.809 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 142.250.27.94 (142.250.27.94) 29.093 ms * *

 

Highlighted
Chat Champion
BTW, I should have mentioned that during the ping and traceroute tests my download speed was between 1.5 and 10Mbps and has been for around 30 mins. Prior to that speeds were up in the high 40s. Current line sync speed is 70185 Kbps and reported attainable download speed is 58106 Kbps.
Highlighted
Community Team - TT Staff

Hi Doodah,

 

Thanks for running the tests

 

Do you have another router you can test with? If not then we can arrange to send one

Chris

Highlighted
Chat Champion

Hi Chris,

 

I only have an HG633 router that is VDSL capable. Do the results of ping and traceroute tests indicate a possible router problem ?

Highlighted
Community Team - TT Staff

I don't know about a fault with the router but the first hop in the traceroute is higher than we would expect, is 192.168.50.1 your router?

Chris