Thanks for reaching out.
This isn't behavior we've come across before, and we'd *love* the opportunity to dig into things a bit further to see if we can get to the bottom of what's causing it. If possible, would you be able to submit a support ticket to us from your instance of PingPlotter (via the "Help" -> "Email PingPlotter Support" option)? This will give us a look at what version of PingPlotter you're running, as well as any error logs that may be present - which may help provide some clues into what's causing this to happen.
Let us know, and we'll be happy to help out from there!