Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google DNS Glitch Caused Outage

Posted by CmdrTaco on from the not-much-else-happens-on-sunday-morning dept.

An anonymous reader writes "Google suffered a pretty long outage saturday evening, due to some DNS glitches, according to company spokesperson. All Google services were down for a while, including Gmail and Google AdSense. There seems to be a DNS hijack, as some screen grabs show that Google.com was redirecting to another site, SoGoSearch.com. "

3 of 283 comments (clear)

  1. Re:Whois Entries Not Indicative of a Hack by Megane · · Score: 4, Interesting
    Wow, I thought that trick stopped working like four years or so ago. I even had one of those kind of entries, but took it out when the search stopped showing them.

    Looks like these clowns aren't just limiting themselves to Google...

    AOL.COM.IS.N0T.AS.1337.AS.GULLI.COM
    AOL.COM.IS.0WNED.BY.SUB7.NET
    AOL.COM.CANDICE-CHAMBERLAIN.COM
    AOL.COM.AINT.GOT.AS.MUCH.FREE.PORN.AS.SECZ.COM
    AOL.COM
    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  2. Google didn't cash 400,000 US$ during that time by astrab · · Score: 5, Interesting
    According to gigaom.com, Google acknowledges having suffered a 'DNS blackout' for two hours (aprox) this past Saturday, and users couldn't access the search engine.

    During Q1 2005, Google cashed $657 million by showing sponsored links on search results. This means 300,000 US$ per hour. Taking into account that this issue happened on Saturday (less users), we can estimate the 'non-revenue' figure in 400,000 US$ aprox, without considering other non-working services like Google AdSense, which probably suffered problems during this time.

    http://google-blog.dirson.com/post.new/0260/

  3. Re:SoGoSearch didn't hijack by Dun+Malg · · Score: 4, Interesting
    com.net, net.com, etc should be reserved.

    A better idea is to not have such brain-dead DWIM "features" in the browser. What kind of stupidity is it to blindly append a TLD to a URL that already ends in a valid TLD?

    --
    If a job's not worth doing, it's not worth doing right.