For all that it mentions common misconceptions, the article is still wrong in at least 3 ways: First, traceroutes can, if you control both endpoints, place bou

For all that it mentions common misconceptions, the article is still wrong in at least 3 ways: First, traceroutes can, if you control both endpoints, place bounds on where a network error is. Second, traceroute is useful if there are three endpoints and you control at least 2 of them. Thirdly, you do in fact know something about other people's networks by the mere fact that you've traversed the network before at different times.