TTLatency: Difference between revisions
| Line 26: | Line 26: | ||
==What can be done?== |
==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. |
|||
Revision as of 09:56, 4 April 2017
For a while now we've been seeing latency jumps on TalkTalk connected lines.
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
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.










