Verexio :
bill001g :
You have to be careful about reading too much into ping tests when you have the packet size greater than 1500. That is the maximum that will fit in one ethernet frame if you make the number bigger the packet must be broken down into pieces and send as multiple frames. In most cases you are measuring the cpu overhead when you are doing this.
This number may actually be smaller if you are really wired to a actual modem and not a router. There is some overhead added for things like pppoe but it depends on the technology used. Set the DF flag on the ping command to find the largest packet you can send
If your device is actually a router/modem and you are getting delays pinging that ip then there may be something wrong with the device. You will always see small spikes here and there but not large ones. Most routers have no trouble keeping up with ping.
Now if you really do have a modem when you ping the gateway you are testing the connection between your house and the ISP. Depending on the technology and how the ISP has implemented it you can be sharing this connection with neighbors. Their traffic will cause random delays for yours. It still should not be a lot. What would be more of a issue is if you get actual packet loss since that could be due to a bad connection in the wiring to your house. Most ISP will not admit they have overloaded a connection in their network but they will fix broken wires.
Overall you can not fix delays in the network. It represents distance and your traffic may not flow in a optimum path depending on how your ISP infrastructure is built and how they connect to other isp. You can dig around with tracert and work at finding how things are connected but you can not change anything.
Okay thanks for the info! Does it mean anything that my first hop is always 100% packet loss? I know that there is a server in my town and I'm guessing that that is my first hop.
All that really means is they have their device configure to not respond. That is unfortunate when it is the first hop since that is the most common place for a issue. If it only does not respond to tracert but works for ping then that is not as bad. The first hop should be the same ip as your gateway even though it does not show it. You use tracert mainly to get the IP of the routers in the path so you can issue ping.
The other thing tracert shows you is where the latency in the path is happening. As you say you get 60ms to seattle, you should be able to see which hops are adding the biggest delays. Sometimes by looking at the names of the routers,,,if they have names assigned...you can guess what city the router is in. I have seen very strange stuff on some ISP. You data could do something stupid like go to chicago or los angels before going to seatte. I doubt it is that bad but it is interesting to look at. You can not really change the path other than using a different ISP on your end