FIbre Support

Get expert support with your Fibre connection.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Slow speed in the evening

garytastic
Chat Champion
Message 33 of 33

For the last 3 days I've been getting very slow speeds in the evening.

In the morning it's fine and I get a ping of 20 and download speed of 25Mbps, but come the evening and my ping has gone up to 40 and my speed has dropped to 5Mbps,

This is both wireless and wired also I've tried 2 different routers and the same with both so not a router issue.

Could somebody look into this for me.

Thanks

0 Likes
32 REPLIES 32

Message 21 of 33

Hi garytastic,

 

Thanks for confirming this. I am still looking into this and I'll let you know as soon as I know more.

 

Thanks

 

0 Likes

Message 22 of 33

As you can see on your traceroute, hop 6 times out every time, this is an IP to IP routing error on the back-haul.

IT IS NOT A FAULT as claimed by TT staff - IT IS A ROUTING ERROR in a data centre!

 

BT always used to do the same thing, when it was a routing error they would claim a fault on the line, you'll just have to wait it out till someone in the data centre fixes the routing issue

 

0 Likes

Message 23 of 33

I can confirm that when I did the speed tests there was only one device connected. And this was a wired connection.

0 Likes

Message 24 of 33

Hi garytastic,

 

I've received an update to advise that one of the line tests have detected a potential fault so if all testing has been completed then the next step would be to arrange an engineer visit to investigate further. This would be to look into the overall speed of the connection.

 

In regards to the slow speeds of an evening could I just confirm, is the throughput speed low if you run the speed test with only the one device connected to the line?

 

Thanks

 

0 Likes

Message 25 of 33

Hi the others I spoke to are between 3-5 miles away.

0 Likes

Message 26 of 33

Hi garytastic,

 

I'm still looking into this with our Network Team. Could I just confirm, are the others who are experiencing the same issue around the same area as yourself?

 

Thanks

 

0 Likes

Message 27 of 33

Hi, any update?

I have spoken to others who are on Talk talk but on different exchanges who are experiencing the same issue.

0 Likes

Message 28 of 33

Hi garytastic,

 

Thanks for running these tests. I've passed the slow throughput speeds of an evening over to our Network Team now and I'll let you know as soon as I receive an update back.

 

Thanks

 

0 Likes

Message 29 of 33

Have done the speed tests, ping and trace route as requested and here are the results, These are all wired results.

 

speed1.png

Pinging google.co.uk [216.58.198.163] with 32 bytes of data:
Reply from 216.58.198.163: bytes=32 time=41ms TTL=55
Reply from 216.58.198.163: bytes=32 time=58ms TTL=55
Reply from 216.58.198.163: bytes=32 time=36ms TTL=55
Reply from 216.58.198.163: bytes=32 time=34ms TTL=55

Ping statistics for 216.58.198.163:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 58ms, Average = 42ms

 

racing route to google.co.uk [216.58.213.99]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms TALKTALK [192.168.1.1]
2 28 ms 29 ms 28 ms host-78-151-229-189.as13285.net [78.151.229.189]

3 37 ms 31 ms 30 ms host-78-151-229-188.as13285.net [78.151.229.188]

4 34 ms 34 ms 33 ms host-78-144-11-187.as13285.net [78.144.11.187]
5 34 ms 35 ms 38 ms 74.125.51.108
6 * * * Request timed out.
7 39 ms 39 ms 39 ms 172.253.68.210
8 37 ms 36 ms 35 ms 74.125.242.115
9 36 ms 35 ms 34 ms 216.239.58.131
10 37 ms 40 ms 36 ms 209.85.143.66
11 34 ms 32 ms 32 ms 108.170.246.161
12 35 ms 36 ms 36 ms 216.239.57.121
13 36 ms 34 ms 34 ms lhr25s02-in-f99.1e100.net [216.58.213.99]

Trace complete.

Speedtest3.png

Pinging google.co.uk [172.217.169.3] with 32 bytes of data:
Reply from 172.217.169.3: bytes=32 time=36ms TTL=54
Reply from 172.217.169.3: bytes=32 time=36ms TTL=54
Reply from 172.217.169.3: bytes=32 time=36ms TTL=54
Reply from 172.217.169.3: bytes=32 time=36ms TTL=54

Ping statistics for 172.217.169.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 36ms, Average = 36ms

 

Tracing route to google.co.uk [172.217.169.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TALKTALK [192.168.1.1]
2 30 ms 30 ms 30 ms host-78-151-229-189.as13285.net [78.151.229.189]
3 30 ms 36 ms 32 ms host-78-151-229-188.as13285.net [78.151.229.188]
4 35 ms 35 ms 35 ms host-78-144-11-187.as13285.net [78.144.11.187]
5 36 ms 36 ms 35 ms 74.125.51.110
6 * * * Request timed out.
7 37 ms 38 ms 38 ms 172.253.66.100
8 36 ms 37 ms 36 ms 74.125.242.114
9 37 ms 37 ms 37 ms 209.85.250.185
10 37 ms 36 ms 36 ms 216.239.58.132
11 37 ms 37 ms 36 ms 108.170.246.129
12 37 ms 37 ms 37 ms 209.85.241.93
13 36 ms 36 ms 36 ms lhr25s26-in-f3.1e100.net [172.217.169.3]

Trace complete.

Speedtest4.png

Pinging google.co.uk [216.58.213.99] with 32 bytes of data:
Reply from 216.58.213.99: bytes=32 time=20ms TTL=55
Reply from 216.58.213.99: bytes=32 time=20ms TTL=55
Reply from 216.58.213.99: bytes=32 time=20ms TTL=55
Reply from 216.58.213.99: bytes=32 time=20ms TTL=55

Ping statistics for 216.58.213.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 20ms, Average = 20ms

 

Tracing route to google.co.uk [216.58.213.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TALKTALK [192.168.1.1]
2 14 ms 14 ms 14 ms host-78-151-229-189.as13285.net [78.151.229.189]
3 14 ms 14 ms 14 ms host-78-151-229-188.as13285.net [78.151.229.188]
4 20 ms 20 ms 19 ms host-78-144-11-187.as13285.net [78.144.11.187]
5 19 ms 19 ms 19 ms 74.125.51.108
6 * * * Request timed out.
7 21 ms 21 ms 21 ms 172.253.68.210
8 20 ms 20 ms 20 ms 74.125.242.115
9 21 ms 21 ms 21 ms 216.239.59.77
10 21 ms 22 ms 29 ms 216.239.58.132
11 21 ms 21 ms 21 ms 108.170.246.161
12 20 ms 20 ms 20 ms 216.239.57.121
13 20 ms 20 ms 20 ms lhr25s02-in-f3.1e100.net [216.58.213.99]

Trace complete.

Speedtest5.png

Pinging google.co.uk [216.58.198.163] with 32 bytes of data:
Reply from 216.58.198.163: bytes=32 time=35ms TTL=55
Reply from 216.58.198.163: bytes=32 time=36ms TTL=55
Reply from 216.58.198.163: bytes=32 time=36ms TTL=55
Reply from 216.58.198.163: bytes=32 time=36ms TTL=55

Ping statistics for 216.58.198.163:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms

 

Tracing route to google.co.uk [216.58.198.163]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TALKTALK [192.168.1.1]
2 31 ms 30 ms 30 ms host-78-151-229-189.as13285.net [78.151.229.189]
3 30 ms 30 ms 30 ms host-78-151-229-192.as13285.net [78.151.229.192]
4 45 ms 35 ms 36 ms host-78-144-11-37.as13285.net [78.144.11.37]
5 36 ms 35 ms 35 ms 72.14.208.22
6 * * * Request timed out.
7 38 ms 38 ms 38 ms 172.253.68.214
8 37 ms 37 ms 36 ms 74.125.242.114
9 38 ms 37 ms 38 ms 209.85.250.185
10 37 ms 36 ms 37 ms 216.239.58.132
11 37 ms 37 ms 37 ms 108.170.246.161
12 37 ms 36 ms 37 ms 108.170.232.99
13 36 ms 36 ms 36 ms lhr25s10-in-f3.1e100.net [216.58.198.163]

Trace complete.

Speedtest6.png

Pinging google.co.uk [216.58.213.99] with 32 bytes of data:
Reply from 216.58.213.99: bytes=32 time=34ms TTL=55
Reply from 216.58.213.99: bytes=32 time=35ms TTL=55
Reply from 216.58.213.99: bytes=32 time=35ms TTL=55
Reply from 216.58.213.99: bytes=32 time=34ms TTL=55

Ping statistics for 216.58.213.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 35ms, Average = 34ms

 

Tracing route to google.co.uk [216.58.213.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TALKTALK [192.168.1.1]
2 29 ms 29 ms 30 ms host-78-151-229-189.as13285.net [78.151.229.189]
3 25 ms 25 ms 24 ms host-78-151-229-188.as13285.net [78.151.229.188]
4 26 ms 25 ms 26 ms host-78-144-11-187.as13285.net [78.144.11.187]
5 35 ms 33 ms 30 ms 74.125.51.108
6 * * * Request timed out.
7 36 ms 36 ms 35 ms 172.253.68.210
8 31 ms 32 ms 34 ms 74.125.242.115
9 37 ms 37 ms 35 ms 216.239.58.131
10 35 ms 35 ms 36 ms 209.85.143.66
11 31 ms 31 ms 31 ms 108.170.246.161
12 35 ms 35 ms 35 ms 216.239.57.121
13 34 ms 35 ms 34 ms lhr25s02-in-f3.1e100.net [216.58.213.99]

Trace complete.

Speedtest7.png

Pinging google.co.uk [216.58.206.131] with 32 bytes of data:
Reply from 216.58.206.131: bytes=32 time=36ms TTL=54
Reply from 216.58.206.131: bytes=32 time=36ms TTL=54
Reply from 216.58.206.131: bytes=32 time=36ms TTL=54
Reply from 216.58.206.131: bytes=32 time=36ms TTL=54

Ping statistics for 216.58.206.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 36ms, Average = 36ms

 

Tracing route to google.co.uk [216.58.206.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TALKTALK [192.168.1.1]
2 30 ms 31 ms 31 ms host-78-151-229-189.as13285.net [78.151.229.189]
3 31 ms 31 ms 31 ms host-78-151-229-192.as13285.net [78.151.229.192]
4 36 ms 36 ms * host-78-144-11-37.as13285.net [78.144.11.37]
5 35 ms 36 ms 36 ms 72.14.208.22
6 * * * Request timed out.
7 37 ms 37 ms 36 ms 108.170.238.118
8 36 ms 36 ms 35 ms 216.239.58.223
9 36 ms 35 ms 35 ms lhr25s14-in-f3.1e100.net [216.58.206.99]

Trace complete.

 

I hope that's enough information for you to find out what the issue is.

0 Likes

Message 30 of 33

Hi garytastic,

 

Ok thanks for confirming this. Once we have the speed test and pings and trace results then we can pass the slow speeds over to our Network Team for further investigation.

 

Thanks

 

0 Likes

Message 31 of 33

There are a few reconnections because I've installed a new router as my other one had issues, and it reconnected last night as it had updated the firmware. 

0 Likes

Michelle-TalkTalk
Support Team
Message 32 of 33

Hi garytastic,

 

I'm sorry to hear this and I'll take a look now. I've run a test on the line which hasn't detected a fault, however I can see re-connections on the line. Is the connection also dropping?

 

Could you run a few wired speed tests using the TalkTalk Speedtester when the speed is ok and also when the speed is  low. Can you also run a wired ping and trace route when the speed is good and when this drops and post the results into the thread.

 

Run a Ping or Traceroute

 

Thanks

 

0 Likes