![]() Wherever that is first introduced in the route is usually a good indiator of where your issue is whether that's in your local network, your ISP's network, or somewhere further upstream. When you start to see red packet loss or high spikes in latency, work your back through the route until you identify where that pattern beings. This same method can be applied to about any situation. This is a really good indicator that the issues you're having start in your ISP's network. We leave hop 1, 2, and the final destination open to show where the route is good, and where it starts to go bad, and that the final destination is affected by what's happening earlier in the route. If you open the timeline graphs for each hop (double-click on the hop number), working your way back through the route, you'll find that the pattern of latency and packet loss starts at hop 2 as shown in the graph above. However, we can get even more specific with the specific hop that is giving us grief. Sending our ISP this graph will probably get a tech to come out and run some tests. Remember: red is bad! We can see here that we regulularly get packet loss tyring to reach out final destination. The response time for the last packet sent. This average ignores timeouts and lost packets. Latency Graph Average latency for the current focus period. This shows the total time it takes to send a packet from your device to the target and back. This second graph starts painting a different story. Round Trip A simplified set of data for the target of your trace. no downloads, streaming audio, on-line game playing, etc. This first graph shows what the traceroute should look like with no load on the connection, i.e. ![]() they take that router down for maintenance or you get load balanced onto another router) you really have no idea what happened. ![]() If you're tracing to the border router and your route changes (i.e. One common mistake we see folks make is that they'll trace to their ISP's border router. It's widely available and accessible in most cases. If you're not sure what to target, 8.8.8.8 Google DNS is usually a good place to start.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |