I'm not *exactly* sure what problem you're describing here, but I think it has to do with a defect in version 2.03.<br><br>Currently, in 2.03, if there are too many outstanding requests (which can easily happen if you have a questionable network and a fast trace interval (< 5 seconds)), it puts some traces out in a queue and then "forgets" about them. This causes the response to never return - and then the graphs get out of sync. It's a bit annoying.<br><br>This has been fixed in the latest beta (version 2.03.1 beta 4) which is available to all registered users.<br><br>If this *isn't* the problem you're describing, let me know.<br><br>