By the way, for those who want to contend it is an AT&T issue.
First off, if it was an AT&T issue, it would effect every player, regardless of which ISP they were coming from.
Secondly, if it was a fat-fingered route table for Comcast being propagated from AT&T, it would be in Comcast's best interest to get it fixed.
Thirdly, if it is a fat-fingered route table in Comcast, for the AT&T block of IP addresses, they are still the only ones who can fix it.
Does it mean AT&T is not to blame at all? No. It means the both AT&T and Comcast need to be told about things like this so they can finally get together and fix it. Pointing fingers is really an exercise in futility in these types of problems.
The problem with both of these companies, is their arrogance is just as big as they are. They will not pay attention to one user who is having a problem. That is why it takes a flood of calls to make things happen. In their minds, they can do no wrong at all. They will always put the burden of proof on the end user when there is a problem.
I would find some validity in this, as the issue is usually PEBKAC error and a waste of tech support time to fix a problem. I find this at work a lot. "Dan, my POS computer is broken. Can you come up and fix it?" It is usually something stupid.
I also encountered this a lot at a mower shop that I used to work at.
CUSTOMER: "My mower wont start"
ME: "Is there gas in it?"
CUSTOMER: "Of course I put gas in it, do you think I'm an idiot?"
ME: "Not at all, sir, but that is the first thing in a mechanic's troubleshooting list. I'll send someone over to pick it up"
They get really pissed when they get a bill for $60. ($50 p/u and delivery fee and $10 for the fuel)
Unfortunately, they (tech support folks) are oftentimes very rude to the end user and have an attitude of they know soooo much more because their little tech support flow-chart book imbues them with more knowledge than a "normal" person.
But, as you say, a flood of calls cannot be ignored.
