TTLatency: Difference between revisions

From AAISP Support Site
Line 13: Line 13:
Here are some examples:
Here are some examples:


<gallery mode="nolines" widths="1005" caption="Example graphs">
<gallery mode="nolines" widths="1005" caption="Example graphs showing latency jumps">
TTLatency1.png|Jump down at 9am
TTLatency1.png|Jump down at 9am
TTLatency2.png|Jump down at 8pm
TTLatency2.png|Jump down at 8pm

Revision as of 12:04, 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:

How does this affect customers?

The impact is usually low or zero. A few extra milliseconds is not noticed in practice by most customers, it's not enough to impact the majority of services, VoIP will still work unaffected etc.

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.