| Test Type: | Application Speed |
| Location: | | | Download Speed: | 8108 Kbps | | Upload Speed: | 666 Kbps | | Speed Consistency: | 12 % | | Round Trip Time: | 13 ms | | Max Delay: | 537 ms | | Average Delay: | 2 ms | | Bandwidth: | 16000 Kbps | | Max Route Speed: | 40329 Kbps | | Route Concurrency: | 2 | | Test Type: | h / h | | Glossary of Results |
|
Need help with these results? Contact us.
4 connection problems found, click the  to learn more.
MSDL01: The download speed is too low for the latency/bandwidth of the connection
This means that download throughput has been recorded lower than the attainable speed for the connection being tested and this degradation is not accounted for by the latency of the connection. This indicates that the connection has data flow interference through congestion or regulation problems.
A high TCP Max Delay and/or a low Data Flow QoS will also confirm any occurrence of data flow quality problems.
Learn More
|
MSBW01: Bandwidth is much lower than speed attainable for the route being tested.
This means that the trip latency between the client and server is able to support connection throughput speed that is much greater than the bandwidth provided. This is more of an observation than a problem but it does indicate that if you had a faster bandwidth service then this route would be able to deliver faster throughput up to the max route speed.
Learn More
|
MSTR01: The data flow for this test is too erratic
Although the speed achieved may match expectation for the connection, a low data flow QoS score means that the data flow between the server and the workstation was not consistent. There can be several reasons for this such as data congestion along the route or data loss which invokes recovery. The lower the QoS percentage, the more erratic the data flow. Many applications can be severely affected by poor data flow quality regardless of data throughput speed, for example media applications such as video or voice may become jerky. Voice (VoIP) telephony will become garbled. If you suspect that the connection was in use by another application try running the test again to validate if the problem is persistent. Learn More
|
MSMD01: TCP is waiting too long for data
The test recorded a TCP maximum delay that exceeded the natural TCP forced idle delay as a result of the connection's trip time. This indicates that there may be problems with consistent data flow between the server and the client. A poor data flow QoS reading is also likely if the max TCP delay is much higher in comparisons to the trip time. Common reasons for this type of problem are packet loss and duplicates. The test graph view will show the TCP delay over the time of the test. Height and width of the 'orange' delay line shows the delay consistency. Learn More
|
|
|
