Did anyone actually look at Pands ping plot? The whole reason is right there.
Notice the 30% packet loss, and large variability on the last hop right before HTC?
Thats a clear sign of an asynchronous route thru his service provider. Which means that the packets come to HTC thru one path, and go back thru another. And the route back can only be pinged from the HTC end to check for its own problems.
30% packet loss is BAD all on its own, but the odds are that you also have an asynch route which adds its own problems. Go back and search for this problem in the Connection forum, and read the replies from Scuzzy. Just because you have DSL don't mean your connection is somehow magical (and the same goes for cable).
Hmmmm... let me bet that your problems get worse during prime time?
Oh and stop acting like an ass, Pand.