Bad first hop
I have latency and packet loss problems with my first hop, which is an sbcpacbell server that is owned by AT&T (AT&T bought SBC Pacific Bell). On occasion, these problems go away, but, usually, they are apparent. The trace route (shown below) shows that the first hop is the source of most of the incurred latency. I also have a static IP, which may contribute to my issue, as there is perhaps less flexiblity in my initial routing from the Central Office. I am paying for 6 Mbps down and 1.5 Mbps up; my speeds are currently ranging from 2.5 to 5.5 down and 0.7 to 0.08 up. I have had 3 inside techs in the last 2 weeks and 1 outside tech, none of which have located any problems (although I did have a useless filter removed and some wiring cleaned up). One tech replaced my NGV-510 router with a NGV-5031, which didn't help the internet connection at all, and actually made the inside wireless connections more problemmatic; I have since reverted to the 510. I have attached a pingplotter output as a nominal example that shows latency and lost packets in the bottom graph, with a trace route in the top half.
It appears to be impossible to get any U-verse assistance other than another useless inside or outside tech visit (anothe schedule for tomorrow). I figure after AT&T spends the money for 20 or more visits, somebody at AT&T might notice. I am really beginning to regret switching to U-verse from my regular AT&T phone line with ADSL.