Today, Comcast gave us all a perfect example of the abuses that can occur when net neutrality is not legislated. The long version along with updates can be accessed via the title link. The short version is that Comcast users this morning found that they could not access any of Google's services. Gmail, Adsense, Adwords, and Google Calendar were immediately affected while Youtube was also reported as not working. Those who called Comcast were first told not to use Firefox, since Comcast doesn't support any browser but Internet Explorer. When that line failed, they would tell users that Windows settings were to blame (Firewall, Anti-virus software, Windows Update were among the services initially blamed). In the event that a customer was fortunate enough to make it past that line of defense, Comcast simply blamed Google and said that it was down.
So where's the kicker? Well, if you used the ip address instead of the domain name you could access the services without issue. If you were using some other provider, you could access Google. If you were using a VPN to go through another connection you could access Google.
Update: Evidently Comcast had a DNS server issue in MA and has taken it offline to fix the problem. Most of the affected users are now able to access Google. Any requests for a refund or partial refund are being denied.
I had Comcast here in Utah for awhile. Yes, the speed was good (at the time, 1.5Mbps) but the cost was outrageous and the service nonexistent. I'm fortunate enough to live in an area with an independent telco that has committed to DSL and will be offering FTTH within a year or two. Incidentally, this kind of thing will become commonplace without net neutrality legislation. If you can make a buck from tying enough tubes and slashing enough Internet dumptruck tires...
Tuesday, September 26, 2006
Subscribe to:
Post Comments (Atom)
2 comments:
It was not a DNS issue - my machine's configured to use OpenDNS and Google was still inaccessible. A check in ethereal verified that Firefox had successfully contacted the server, but wasn't getting a valid response.
are you able to access Google now? Were you able to access Google using the ip address instead of the domain name? out of curiousity, what ip address was returned for google at the time and does it match with google's range?
Post a Comment