WWTBAM Bored

I am having what I think is a unique internet problem.

Last Friday I switched internet providers, moving from Charter to AT&T Uverse. I was concermed about speed because with Charter I was getting on average 45Mbps download speeds (when it was up) and AT&T would only provide “up to” 18Mbps in my area. After AT&T was installed I tested the speed and am consistently getting 18ish Mbps.

Once on Uverse, I noticed that Yahoo, Facebook and ATT.com of all things would not load, or loaded after a very long time. Usually they would not load. I was just get the “waiting for att.com” status, but never a 404 error. Other sites such as MSN, BankofAmerica, GOOGLE, the local newspaper and TV stations, Amazon would all load normally (adjusted for 18 Mpbs as opposed to what I was used to).

This problem occurs on both home computers (IE and Firefox), both Ipads (safari only), and all Iphones when connected to the home network. The problem does not happen on my son’s Galaxy phone or my wife’s Macbook Pro (safari or firefox).

The problem does not happen on the home computers or Ipads when tethered to one of the Iphones as a hotspot.

AT&T is sending a technician out tomorrow but I can’t figure out where the problem might be.
If it was my computer (or other devices), seems they wouldn’t work tethered (or when they were on Charter). If it was Uverse, then my wife’s Macbook and son’s phone should work.
Confusing. Anyone with ideas?

What would make Yahoo act different from MSN or Bing? Facebook different than Youtube? Why would they behave different depending on the network I’m going through? Why does the Macbook Pro or Galaxy not have an issue?

How that heck did you get 45M bps on a cable modem?! I've never heard of anything that fast except for business systems.

The problem is very probably that AT&T is having routing problems. Excuse me if you know how TCP/IP works already but it must do many "hops" from router to router to get to where you want to go. One major trunk line is probably down. It is probably just on your area or we'd be hearing about it on the news.

Use http://www.dslreports.com/speedtest?flash=1 to test your speed to various servers around North America. You probably will find some are very slow or unresponsive.

Also do you know about TRACERT? Open a DOS window and enter "tracert http://www..... and you'll see all the hops to your destination. If some keep timing out there's where your problem is.

Bob Juch wrote:How that heck did you get 45M bps on a cable modem?! I've never heard of anything that fast except for business systems.

The problem is very probably that AT&T is having routing problems. Excuse me if you know how TCP/IP works already but it must do many "hops" from router to router to get to where you want to go. One major trunk line is probably down. It is probably just on your area or we'd be hearing about it on the news.

Use http://www.dslreports.com/speedtest?flash=1 to test your speed to various servers around North America. You probably will find some are very slow or unresponsive.

Also do you know about TRACERT? Open a DOS window and enter "tracert http://www..... and you'll see all the hops to your destination. If some keep timing out there's where your problem is.

I'll check that out later tonight. Thanks for the input. I figure its a routing type issue but still baffled by it not affecting the MacBook or Galaxy phone.

Bob Juch wrote:How that heck did you get 45M bps on a cable modem?! I've never heard of anything that fast except for business systems.

The problem is very probably that AT&T is having routing problems. Excuse me if you know how TCP/IP works already but it must do many "hops" from router to router to get to where you want to go. One major trunk line is probably down. It is probably just on your area or we'd be hearing about it on the news.

Use http://www.dslreports.com/speedtest?flash=1 to test your speed to various servers around North America. You probably will find some are very slow or unresponsive.

Also do you know about TRACERT? Open a DOS window and enter "tracert http://www..... and you'll see all the hops to your destination. If some keep timing out there's where your problem is.

I'll check that out later tonight. Thanks for the input. I figure its a routing type issue but still baffled by it not affecting the MacBook or Galaxy phone.

Bob Juch wrote:How that heck did you get 45M bps on a cable modem?! I've never heard of anything that fast except for business systems.

The problem is very probably that AT&T is having routing problems. Excuse me if you know how TCP/IP works already but it must do many "hops" from router to router to get to where you want to go. One major trunk line is probably down. It is probably just on your area or we'd be hearing about it on the news.

Use http://www.dslreports.com/speedtest?flash=1 to test your speed to various servers around North America. You probably will find some are very slow or unresponsive.

Also do you know about TRACERT? Open a DOS window and enter "tracert http://www..... and you'll see all the hops to your destination. If some keep timing out there's where your problem is.

I'll check that out later tonight. Thanks for the input. I figure its a routing type issue but still baffled by it not affecting the MacBook or Galaxy phone.