WINMTR giving very weird results

[Givemema]

Hey.

Hopefuly I can get some help from you guys.
Lately I've been having some issues in gaming.

I've ran multiple WINMTR pings, but always on intervals of 1 seconds.
All those pings came back looking just fine.

Then I decided to change the intervals to 0.1, and I started getting weird results.
Look at this:
http://i.imgur.com/bpgPgRj.png
My router seems to have loss and the number of pings sent is just too low.

I also tried with 0.01 intervals:
http://i.imgur.com/N0oLmJd.png
This is even weird. Different numbers for every hop.

I am connected with CAT6, no wifi or anything, so these results are as accurate as it gets.

Is there a problem with my router, my ISP, both, or are these just WINMTR bugs?

 

[bill001g]

I would not worry about it. There is either a problem with the tool or the router is just designed to not respond quickly enough to pings. Ping is considered a low priority thing compared to regular traffic. The router is doing a great job of sending traffic to the nodes past your router.

Let say you had 100% loss. If all traffic was actually being dropped by your router every hop past the router would also have 100% loss ...how could it get past.

Since there is no problems in the hops beyond your router it is just one of those strange things that happen. This can happen at any node in the path actually.

A trace that show issues will show the issue at a certain hop and that issue will appear in every hop past and many times get worse.

 

[Givemema]

Thanks for the answer.

Look at the 0.01 intervals:
http://i.imgur.com/N0oLmJd.png

Is this also OK?

 

[bill001g]

Your average latency to actual hops is very small so that means everything is likely fine.

 

[Givemema]

What about the difference between the average and the worst pings on some of the hops? is that OK?
Seems like I have some spikes from time to time.

 

[bill001g]

All that means is those intermediate routers are too busy to bother with your stupid requests

Response to ping and tracert are not considered high priority traffic. You can not read a lot into any numbers you see. The averages are a much better indicator.

Still lets say you find a problem what can you possibly do. You can't call a ISP that is not yours. Even the ones in your network the ISP will just laugh at you if you complain about a few extra ms of delay. They have much more serious issues.

 

[Givemema]

OK. What can I do then, to actually try and see if there are any issues?
Anything that goes deeper than WINMTR?

 

[bill001g]

Maybe you don't have a actual network problem and the game is telling lies. Games ingame ping numbers are affected by the client and the server software. There are cases where the client software gets so busy doing something it will claim their is a delay but what is really happening is the client is incorrectly measuring it because it spent all its time doing something like updating video buffers.

You could try opening some cmd windows and let a actual continuances ping command run to the first couple hops in that trace. When the game claims there is a issue you could check and see if the ping also see problems.

I suspect it is some setting in the game causing a fake network problem. Maybe set all the video option on the minimum and see if it makes a difference.