said by whs:
Even though it passed and it says I have 0% loss on top of the most recent test report. It still shows areas where I have packet loss. Mostly on the west coast but still shows some in central as well. Can someone help me understand what the bottom half of the report is saying and what the colors mean? One of the areas is just after my house at the head station and the very last report which otherwise seemed glowing reads to me 7% packet loss on that node. Am I correct?
No color means that packet loss was minimal. Yellow means that it was moderate, but probably not a big deal. Red means that the packet loss was excessive and probably a sign of an issue.
The 7% means that of the 60 packets that were sent, only 56 were return. It doesn't indicate why they weren't returned. The packet may have been dropped at an earlier node on the way there, or on the way back.
Some routers are configured so that they don't respond to ICMP requests, which are what ping and traceroute use. If you had 100% loss, then that's a good sign that's what the "problem" is although that's not a problem really. Partial packet loss can be a sign of an overloaded circuit and traffic with less priority just gets discarded. Or it can be a sign of a flaky connection.
That being said, if the packet loss is happening outside of your network, or your ISP, there isn't a whole lot that can be done other then try to notify that particular hop of the issue, or using different routing.
Will this areas still affect my gaming? So far since comcast reports the problem was resolved my gaming has came back to its normal self. Please take a look at my different tests and tell me if you think my problem is really fixed or if I need to keep looking at it for a bit to be sure.
The tests only tell you the relative quality of the line from a server located on the east, west, or central to your house. It has no bearing on your data unless your data happens to follow the same path.
If you are planing to drive to Chicago from Decatur, what traffic is like or road conditions in Bloomington or Champaign might matter. What traffic is like in San Diego won't matter since there is no reasonable reason why you would drive that route.
If you want to get a better idea what traffic is like between your computer and whatever server you are connecting to, run a traceroute on your computer. Presuming Windows, press WindowsKey-R, type "cmd" and press enter. This should open up a command window. Type "tracert SERVER_HOST_NAME" replacing what the hostname of the server for SERVER_HOST_NAME. The results that are displayed will tell you what each hop your connection is, the IP and/or hostname of that hop, and the 3 response times for that hop. Below is an example from my router to google:
traceroute to www.google.com (18.104.22.168), 30 hops max, 38 byte packets
1 pool-184-17-204-1.ftwy.in.frontiernet.net (22.214.171.124) 3.458 ms 2.628 ms 1.698 ms
2 126.96.36.199 (188.8.131.52) 5.170 ms 3.170 ms 2.701 ms
3 ae5---0.cor01.chcg.il.frontiernet.net (184.108.40.206) 6.021 ms 7.084 ms 6.128 ms
4 ae0---0.cbr01.chcg.il.frontiernet.net (220.127.116.11) 7.299 ms 7.291 ms 6.841 ms
5 18.104.22.168 (22.214.171.124) 17.724 ms 7.227 ms 6.304 ms
6 126.96.36.199 (188.8.131.52) 6.712 ms 38.279 ms 6.482 ms
7 184.108.40.206 (220.127.116.11) 26.315 ms 6.618 ms 6.434 ms
8 18.104.22.168 (22.214.171.124) 29.912 ms 31.757 ms 17.483 ms
9 126.96.36.199 (188.8.131.52) 27.133 ms 27.216 ms 27.179 ms
10 184.108.40.206 (220.127.116.11) 27.072 ms 28.579 ms 27.292 ms
11 18.104.22.168 (22.214.171.124) 27.661 ms 27.854 ms 27.557 ms
12 den03s06-in-f20.1e100.net (126.96.36.199) 27.502 ms 27.113 ms 27.425 ms