I can read traceroutes but I don't use pingplotter much The problems with traceroutes these days is that allot of providers are dropping certain types of requests on routers.
I have an old program that came with Subspace that runs on my desktop called pingroute. Here is the data from that for me, for naval strike.
1 192.168.1.1 Fios_Quantum_Gateway.fios-router.home 0 ms 0 ms 0 ms 6 ms 411 411 0%
2 104.153.105.225 c-104-153-105-225.managed-ded.premium-chicago.nfoservers.com 23 ms 22 ms 2 ms 29 ms 411 411 0%
that's low ping, av ping, high ping, number packets sent, number received and packetloss.
A traceroute is supposed to show you the hops but sometimes doesn't. Like for example this is my traceroute to the naval strike server.. (from windows command line this time)
C:\Windows\system32>tracert 104.153.105.225
Tracing route to c-104-153-105-225.managed-ded.premium-chicago.nfoservers.com [104.153.105.225]
over a maximum of 30 hops:
1 2 ms 1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 24 ms 78 ms 2 ms c-104-153-105-225.managed-ded.premium-chicago.nfoservers.com [104.153.105.225]
Trace complete.
2 hops really? But it's possible to have a low hop count depending on the peering agreements between providers. Maybe nfoservers.com is hosted on the Verizon backbone?
I used to love traceroute and pingroute for troubleshooting. The problem is that even if it does work, if the problem is 5 hops in to a 12 hop path, who are you going to call and complain to? WAY back in the day, almost everyone used the email address
noc@domain.com... so i had about a 70% chance of emailing
noc@middlehopdomain.com and getting a reply. Now that doesn't really work, and even if i don't get a mail bounce for bad address, they could give a shit about me and don't respond.
Now things have grown in size and complexity, and your really only choice of action assuming you don't have local issues, like 1st 2 hops, is to change providers and hope for the best.
2% packetloss for the whole trip is not bad at all. All games these days run on UDP not TCP, which is like streaming video. UDP is a connection stateless protocol that just bursts packets to you. If you get them you get them, if you don't you don't, and when you don't in a game like bf, that's when you see someone skipping a little, or they see you skipping.
Games don't even measure packetloss anymore, because they really don't care. Packets aren't going to be resent. So they focus on latency (packet transit time) and kind of assume that if your ping is low you have a good connection. The reality is if your ping is low, but your packetloss is high, you're lagging like a bitch
