TTLatency: Difference between revisions
mNo edit summary |
m (→Introduction) |
||
| Line 4: | Line 4: | ||
==Introduction== |
==Introduction== |
||
We see latency jumps on TalkTalk connected lines. |
|||
==Purpose of this page== |
==Purpose of this page== |
||
Revision as of 11:58, 4 April 2017
Timeline
2017-04-07 - Page created showing examples and giving a brief description of the problem.
Introduction
We see latency jumps on TalkTalk connected lines.
Purpose of this page
This page will be updated with information about the issue, we will also open a Status page to go along side this page.
Examples:
Here are some examples:
Jump down at 9am
Jump down at 8pm
Jump up at 10am
Jump down at noon
Jump down at 1am
Jump down at 1am
Jump up at 9pm
Jump up at 3pm
Jump down at 10:30am
Jump up at 1am
Jump down at 6pm
How does this affect customers?
When does this happen?
This typically happens when a lines is moved between LNSs at our side.
Why does this happen?
In simple terms, TalkTalk run a ring network, and traffic and go around it one of two ways. One direction is shorter and the other longer - hence if your circuit is being routed on the longer path, then the latency will be higher.
What can be done?
We don't have any control over the route your circuit will take, so in some ways it it pot luck as to which path you are on. However, TalkTalk are wanting to improve this and we are working with them on this project.