> Some chip makers have hidden latency and jitter issues from common tests that are in use by consumers and even ISPs. Ping CANNOT be used reliably to test for latency or jitter.
It's very frustrating because nowhere on that page is there a list of which modems have the bad chips and which don't. Which doesn't help at all with the most obvious way to fix this problem: stop buying modems with the bad chips. Many people (myself included) don't trust the cable modems our ISPs provide, or don't want to pay a monthly rental on one, when we can just buy one for ourselves. If people like me had information on which modems not to buy, we could help to exert market pressure. Why do people think that the only way to fix a problem like this is to complain to the company that created it in the hope that they'll fix it out of the goodness of their hearts? When has that ever actually worked?
> The Intel Puma 6 and Puma 7 chipsets have a performance issue in a part of the packet processing that is specific to TCP/IP, which went undetected for awhile because "ping" packets are not TCP/IP. [...]
(And/or because just running "ping" a few times might not catch the issue if it doesn't happen at the same time as the lag spike.)