Latest revision as of 00:20, 18 August 2018

Using our CQM graphs can give you a good idea as to what could be causing a line to be slow.

You can take a look at your graph and compare it to the examples below to see if there is a match.

Accessing This Feature

Access is via the Control Pages as follows:

Log in to the Control Pages with your xxx@a login
Click on the line you want to view
Clicking on the graph again will show a 7 day's worth of graphs with options there to view 30 and 60 days

Examples

Below are a few examples of slow lines and their graphs.

Lots of traffic on the line

Here is an example of a CQM Graph with lots of upload traffic,

Lots of upload in the morning - a backup without any traffic shaping on the client end. This will make the line slow, but is not a fault

This line is doing a large backup from just before 6am. The dark red horizontal line shows the traffic, during this time there is lots of packet loss (red) and the light blue at the bottom is showing high latency. So, whilst the backup is happening the line has about 50% packet loss and around 300ms of latency. Using the line for things like web browsing at this time will be slow and sluggish. However, this is not a fault per-se. It is normal for a line to appear slow when it's being filled with traffic.

However, this traffic may be unknown, it may not be a backup, but could be a virus or peer-to-peer traffic, or almost anything!

Dealing with Lots of traffic

Try to identify what the traffic is: You can do a Traffic Capture
If it's upload traffic, try unplugging devices on the network until the traffic stops
Contact Support for further help

Packet loss on the line

Packet loss is shown as dripping red from the top on the graph. Here are some examples:

Heavy packetloss. Packet loss on an idle line is always bad news...

...even if only 1% (one red dot at the top is 1%). A line with 1-3% loss

If you suspect you have packet loss, also see:

Packet Loss - a page with more (slightly technical) details about packet loss
CQM Page - Our general page about graphs with Packet Loss examples

Dealing with Packetloss

Run through the ADSL Checks particularly:
1. Plug router in to test socket
2. Check phone line for noise, buzzing/hissing
Run line diagnostic tests
Contact Support

Congestion

If it seems slow in in the evening then it could be congestion somewhere between you and AAISP, or (rarely) within AAISP. A line with congestion may look something like this:

Dealing with Congestion

Contact Support

Line dropped and speed changed

line dropped and came back slower and with higher latency

This line dropped at 01:50, and came back within a minute or two, however, the speed has dropped (horizontal black line at the top) and also the latency (blue at bottom) has increased. There could be a fault here, but in this case we can clearly see that something has happened. If your line has changed in speed and is shown on the graphs, then diagnostics may find a fault, and the Support Team can help.

What Next?

Go to the next step on Slow ADSL Page.

@@ Line 2: / Line 2: @@
 You can take a look at your graph and compare it to the examples below to see if there is a match.
+{{CPbox|#Click on the line you want to view
+#Clicking on the graph again will show a 7 day's worth of graphs with options there to view 30 and 60 days}}
+=Examples=
+Below are a few examples of slow lines and their graphs.
 ==Lots of traffic on the line==
 Here is an example of a CQM Graph with lots of upload traffic,
-[[File:CQM-FTTC-upload.png|none|frame|Lots of upload in the morning - a backup without any traffic shaping on the client end]]
+[[File:CQM-FTTC-upload.png|none|frame|Lots of upload in the morning - a backup without any traffic shaping on the client end. This will make the line slow, but is not a fault]]
-This line is doing a large backup from just before 6am. The dark red horizontal line shows the traffic, during this time there is lots of packet loss (red) and the light blue at the bottom is showing high latency. So, whilst the backup is happening the line has about 50% packet loss and around 300ms of latency. Using the line for things like web browsing at this time will be slow and sluggish.  However, this is not a fault per-se. It is normal for a line to appear slow when it's being filled with traffic. However, this traffic may be unknown, it may not be a backup, but could be a virus or peer-to-peer traffic. You can do a [[Traffic Capture]] to see what the traffic is, or ask Support to Help.
+This line is doing a large backup from just before 6am. The dark red horizontal line shows the traffic, during this time there is lots of packet loss (red) and the light blue at the bottom is showing high latency. So, whilst the backup is happening the line has about 50% packet loss and around 300ms of latency. Using the line for things like web browsing at this time will be slow and sluggish.  However, this is not a fault per-se. It is normal for a line to appear slow when it's being filled with traffic.
+However, this traffic may be unknown, it may not be a backup, but could be a virus or peer-to-peer traffic, or almost anything!
-==Sync rate has been capped or lowered==
-You can check the linerate of your line - this is the speed of the line as reported to us by the back-haul provider.
+===Dealing with Lots of traffic===
-Examples:
+#Try to identify what the traffic is: You can do a [[Traffic Capture]]
+#If it's upload traffic, try unplugging devices on the network until the traffic stops
-[[File:Linerate.png|none|frame|Line rate as shown on the control pages, ie 39.8M - Good!]]
+#Contact Support for further help
-[[File:Linerate-slow.png|none|frame|This one has a rate of 338k - something is wrong!]]
-#Log in to the Control Pages
-#The line rate is usually shown on the front page, as per the image above
 ==Packet loss on the line==
@@ Line 29: / Line 29: @@
 [[File:CQM-heavyloss.png|none|frame|Heavy packetloss. Packet loss on an idle line is always bad news...]]
-[[File:CQM-lowloss.png|none|frame|...even if only 1% (one red dot at the top is 1%). An FTTC line with 1-3% loss]]
+[[File:CQM-lowloss.png|none|frame|...even if only 1% (one red dot at the top is 1%). A line with 1-3% loss]]
 If you suspect you have packet loss, also see:
 *[[Packet Loss]] - a page with more (slightly technical) details about packet loss
-*[[CQM Graphs#Heavy_Packetloss|CQM Page]] - Our general page about graphs with Packet Loss examples
+*[[CQM Graphs#Heavy Packetloss|CQM Page]] - Our general page about graphs with Packet Loss examples
+===Dealing with Packetloss===
+#Run through the [[ADSL Checks]] particularly:
+##Plug router in to test socket
+##Check phone line for noise, buzzing/hissing
+#Run [[Slow ADSL Diagnostics|line diagnostic tests]]
+#Contact Support
+==Congestion==
+If it seems slow in in the evening then it could be congestion somewhere between you and AAISP, or (rarely) within AAISP. A line with congestion may look something like this:
+[[File:CongestionTT.png|none|Frame|Congestion in the evenings, latency occurs in the evenings, during the day is fine]]
+===Dealing with Congestion===
+#Contact Support
+==Line dropped and speed changed==
+[[File:CQM-speed-change.png|none|frame|line dropped and came back slower and with higher latency]]
+This line dropped at 01:50, and came back within a minute or two, however, the speed has dropped (horizontal black line at the top) and also the latency (blue at bottom) has increased. There could be a fault here, but in this case we can clearly see that something has happened. If your line has changed in speed and is shown on the graphs, then diagnostics may find a fault, and the Support Team can help.
+==What Next?==
+Go to the next step on [[:Category:Slow ADSL|Slow ADSL Page]].
 [[Category:Slow ADSL|3]]