Every night we analyse the loss and latency measurements we have taken from all of our broadband lines during the day and we automatically look for patterns that suggest congestion or problems within the core network.
Permission is granted for news/media and other ISPs that are also affected by these issues to republish these findings with attribution to AAISP. XML
Current broadband congestion or fault areas
|Not detected since Sun 26 Jun:-|
|BT 21CN||AY-SU, all BRASs||0.10%||Packet loss approx 8pm to 10pm|
Method of analysis
Every line is sent an LCP echo every second and loss and latency measured. This is summarised per 100 second sample and archived for every line for each whole day. The previous day is then analysed each morning and the above table is updated.
Each line is considered to pass, fail or be inconclusive. Inconclusive includes lines where samples have too much upload or download which could themselves cause higher loss or latency to be observed. Lines with less than 18 hours on-line are excluded totally.
Latency is considered against a reference base-line latency for the circuit, and this has to be present for several hours to be considered. As such, lines without clean latency monitoring (some makes of router) are excluded.
For an area to show in the above table there must be no lines that pass at all, and at least 50% of the lines must fail (the rest being inconclusive). Where we have very few lines we require 80% to fail (and none to pass) to show on this list. The area must also have enough lines, so some smaller exchanges will not be detected.
The size stated is what percentage of our total lines are in the affected area.
The block graph under each report for yesterday is based on an average of valid samples for each line for each hour, and then taking the lowest value of all lines in the affected area, so the loss and latency shown is something that is affecting every line in an area.