at&t dsl congestion in silicon valley?
Poor speed and balky browsing here in Sunnyvale CA, starting on 8/28, still going on as of 9/24. Basic DSL, 768K/384K. Problem seems to be congestion in AT&T network, not DSL line problem. Pings to first hop are consistently excellent, low latency (12 ms), no packet loss. Pings elsewhere are inconsistent, wildly varying latency, lost packets. Some web sites are consistently okay, most are balky and either fail to load or take forever to load. File downloads balky. Video unwatchable, runs for a few seconds, then halts, then runs. All the usual speed-test sites show only a fraction of the specified bandwidth -- not suprising, the test starts/stops as it runs. Behavior unaffected by changing modem, fixing different DNS servers, etc. AT&T tech support friendly but unable to solve, they run the usual line tests, all fine. Have had the service since Mar 2008, always been solid until now.
NormanSI gave her time to steal my mind awayPremium,MVMReviews:
San Jose, CA
said by svmike :From December, 2011 until August, 2012 I was mostly on 768k/384k AT&T Internet due hospitalization and housing issues. For a user who started on 1536k/128k Pacbell DSL, and ultimately switched to Sonic.net, LLC DSL (at 5800k/600k), I found that 768k/384k period extremely painful. I avoided YouTube because of the buffering issues (non-existent even on 1536k/128k).
Poor speed and balky browsing here in Sunnyvale CA, starting on 8/28, still going on as of 9/24. Basic DSL, 768K/384K.
Congestion is the likely culprit. AT&T is deploying ADSL2+/VDSL IPDSLAM ("U-verse Internet") service, and decommissioning their legacy ADSL hardware as much as possible. And they are making sure that U-verse has adequate bandwidth; probably at the expense of legacy ADSL customers.
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum