I've seen this happen many times lately and I have always checked the pings. It has nothing whatsoever to do with internet traffic: it's entirely host related. For example- it once took me 4 minutes and 47 seconds to reach the tower after exiting. During all that time I was at the center of the map seeing accurate plane movements and having a flatline low ping time. These aren't 'warps' where plane positions are jumpy- those are always smooth. Its lack of update for less 'critical' data- kills, deaths, things blowing up, exits, text, etc.
I would jump to the conclusion (not supported with much data) that the new antiwarp code (which works very well to reduce microwarps for close targets) has an algorithm that 'delays' less critical packets to make room for plane position packets. Perhaps this code has a minor bug that allows 'less critical' information to continually get postponed by 'critical' plane packets and put off for way too long. I suspect it will probably be fixed soon in the host code once they have time to figure it out by looking at logs of high usage periods.
There is no doubt, however, that something is happening at the host end and when it does it is a bit like flying into the Twilight Zone.
