Anyone – even users with zero networking experience – can run a traceroute. All you need is a command prompt and a destination device. Yet, despite how easy it is to use, its results are often misunderstood.
To be able to make good use of traceroute for network troubleshooting, you need to understand two things:
- How traceroute works (I covered this in a previous post, and highly recommend reading it first if you need a refresher on what happens behind the scenes), and
- factors that affect the outcome of a traceroute.