Hi.

It's always possible that there's an odd situation that PingPlotter is misinterpreting, although there's no known problems around this topic currently. This definitely sounds like behavior we don't like!

Can you do a save of the period where you're seeing inconsistencies (File -> Save sample set...) and email that to support@pingplotter.com? Also, please send us your pingplotter.ini file. Another very useful piece would be a tracert output of the problem period showing the proper timeouts.

With that data, we may be able to come up with an explanation and/or solution.

- Pete