Pingplotter lol11/7/2023 ![]() In other words, you don't have an easily identifiable problem at hop X further up the route that is mucking up the rest of the route downstream. One clue that this is happening is that you'll have a great trace up until the last one or two hops on your trace. By definition traceroute doesn't take these types of routes into account and, unfortunately, PingPlotter isn't going to be able to tell you about problems with the return route in these cases. If your inbound traceroute traffic is taking a different route back to you than the outbound traffic to the server, this is called an asymmetrical route.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |