Hey razed,

Often when we see this kind of behavior in PingPlotter, it's an indication that *something* pretty close to home (a firewall, some zealous virus scanning software, etc) is locking down on network traffic, and preventing the program from being able to collect any data.

We've actually got a knowledge base article that goes over this exact scenario (as well as provides some ideas for getting things working as expected). Have a look here:

http://www.pingman.com/kb/27

If this leaves you with any questions, or if you need any other assistance - just let us know!

Best wishes,

-Gary