TTLatency: Difference between revisions

(3 intermediate revisions by one other user not shown)

Line 3:

==Timeline==

2017-04-07 - Page created showing examples and giving a brief description of the problem.

⚫

2017-10-21 - Added a note about a potential longer term fix (bottom of page)

⚫

2017-10-21 - Added a note about a potential longer term fix (bottom of page)

TalkTalk have told us (unofficially) that they have a project to help with the latency jumps described here. The project involves using optimised (lower latency) routes rather than random routes - they hope to have this work completed early 2018.

==Introduction==

Line 14:

Line 13:

==Purpose of this page==

This page will be updated with information about the issue and will show examples, we will also open a Status page to go ~~along side~~ this page.

This page will be updated with information about the issue and will show examples, we will also open a Status page to go alongside this page.

==Examples:==

==Examples==

Here are some example graphs from our line monitoring. The latency is shown as the blue line at the base of the graph, and a change is shown as it increasing or decreasing by a few pixels.

Line 46:

Line 45:

==What can be done?==

We don't have any direct control over the route your circuit will take within the TalkTalk network, so in some ways it it pot luck as to which path you are on. However, TalkTalk are looking in to this to see is it's possible for any improvement. We are helping them on this project.

We don't have any direct control over the route your circuit will take within the TalkTalk network, so in some ways it is pot luck as to which path you are on. However, TalkTalk are looking in to this to see is it's possible for any improvement. We are helping them on this project.

A temporary fix may be to adjust the case of your username befiore the @ part in your router settings. Eg, if your username is customer@a.1, then try cuSTOMer@a.1 or some other variation. If you have multiple lines, then make the username match on all of them. This will mean you will connect to a different LNS ar our side, which in turn will change the routing within the TalkTalk network. You may still get re-routed when you log in again next, but you can try the same trick again if that is the case.

A temporary fix may be to adjust the case of your username befiore the @ part in your router settings. E.g., if your username is customer@a.1, then try cuSTOMer@a.1 or some other variation. If you have multiple lines, then make the username match on all of them. This will mean you will connect to a different LNS ar our side, which in turn will change the routing within the TalkTalk network. You may still get re-routed when you log in again next, but you can try the same trick again if that is the case.

This is an unsupported feature. Usually all usernames would be lower case, and our support team may will advise you to change to all lower case in the event of a problem or fault.

Longer term, ~~late 2017 or~~ early 2018, we expect this problem to go away due to works on the TalkTalk network. This is unconfirmed and un tested though, so we have to wait and see.

Longer term, early 2018, we expect this problem to go away due to works on the TalkTalk network. This is unconfirmed and un tested though, so we have to wait and see. TalkTalk have told us (unofficially) that they have a project to help with the latency jumps described here. The project involves using optimised (lower latency) routes rather than random routes.