If this trace shows no packet loss, then hop 1 is not the culprit and you'll need to look at hop 2 and beyond. To verify this, you can trace directly to the IP address of your router (in this case 192.168.1.1) to see if it gives the same pattern. This is normal behavior for a router and does not have an effect on your connection quality. Looking closer at hop 1, we can see a pattern of packet loss that can be explained as your router down-prioritizing ICMP Time Exceeded messages. Hop 1, on the other hand, is starkly different and does not share the same pattern as the rest of the hops. Hops 9 and 10 may vary slightly, but is still very similar. In this example, you can see hops 2 through 12 show nearly identical packet loss patterns. Starting at the final hop, follow the red lines of packet loss up the hops to see where the problem originated. You may also want to right-click and select a different time scale to reduce the amount of scrolling. To begin, open up a Timeline Graph for each hop by double-clicking their rows one by one, starting at the bottom and working your way up to hop 1.Īfter that, you can scroll the Timeline Graph by clicking and dragging with your mouse, using the scroll wheel, or using the slider along the bottom to identify where you see the most packet loss at the final hop. You may also notice that every hop is showing some degree of packet loss. One or more of these things could be occurring, but we’ll step through the troubleshooting process assuming the example above.Īs you can see, we are tracing to the Cloudflare DNS (1.1.1.1) and seeing 1.3% Packet loss on the final hop (Hop 12). Third, it is possible that several of the hops could be down-prioritizing ICMP Time Exceeded packets and showing some packet loss that isn’t “real” (for example, hop 3 above, which is not responding at all). Spitfire Community Representative CCP Hf, EVE Online. More information on how to obtain them can be found here. In the meantime, we would ask everyone affected by this issue to send us your pingplotter and/or traceroute results - it will really help us to tackle the issue. The example above shows a scenario where the router (hop 1) is at 85.5% packet loss, but every other hop does not show the same level of loss. Our engineers are looking into possible ways to mitigate this problem. Some routers just don't prioritize timed out ICMP requests very high (ICMP requests where the TTL equals 0 after reaching them) and this is the case with your router. Second, it is possible that your first hop is down-prioritizing ICMP Time Exceeded packets and the real issue is on hop 2 (which is likely your ISP). In regards to your PingPlotter screenshots you shared, the packet loss you have observed at the first hop is a bit of a red herring. There are a few different issues that could be generating this result.įirst, it may be an issue that starts at your first hop (often your router) and goes all the way through to the final hop. Troubleshooting Packet Loss Across all hops
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |