Another major Comcast outage tonight, this time in the midwest, with Comcast's DNS servers in Chicago apparently going down. After last week's east cost outage, this is most interesting and one might speculate as to what is going on behind the scenes. But the most interesting thing for me at the moment is that the reason I know this is happening is thanks to twitter: my internet goes down, I search Twitter for "Comcast" and not only find out it is more widespread than my home, but also how to fix it (switch your router DNS server address to Google's 8.8.8.8 - see Google's DNS pages for more information on how to set it up).
Note that if you have a wireless router, it's very easy to set up - just log onto your router (usually by going to 192.168.1.1 in your browser - if you don't know your password try admin for the username and password for the password), then go to the basic settings, and somewhere it will say something like "DNS Address: get dynamically from ISP". Unclick this and manually put in the address 8.8.8.8 (Google's server). Restart your router and it should work
Even more interestingly, as of 9.25pm Eastern time, there appear to be no news outlets carrying the story - a search on Google News for "comcast" brings back nothing (although a "realtime" search pulls up the tweets and also shows the increase in traffic referring to Comcast). So Twitter wins again...
I was complaining in the lounge earlier about my Comcast speeds; this is normal during the daytime hours.
ReplyDeleteFantastic goods from you, man.I've understand your stuff previous to and you are just too excellent.I really like what you've acquired here, certainly like what you are stating and the way in which you say it.You make it enjoyable and you still care for to keep it wise.I can not wait to read far more from you.This is actually a terrific website.
ReplyDeletedirectv has the most choices