Quote Originally Posted by Rexxus View Post
Created a thread about this yesterday thinking it was something else entirely.

Are we certain this is not some new change from AT&T? The vast majority in this thread seem to be from the same ISP. Currently in Alabama, but an Atlanta GA location in the VPN fixed things for me immediately.
Could be, with how they're passing things to NTT. I've got less than 20ms on the trace until the trace hits anything related to NTT. Then it goes up to the 50s and then it doubles at the Sacramento node. If not AT&T itself then NTT seems to have a problem there.