Like I was saying… Go Daddy wasn’t hacked or attacked

Guy on twitter says he took Go Daddy down. Press bites.

Yesterday dozens (hundreds?) of “respectable” publications reported that Go Daddy was hacked, and that it was done by a hacker who was part of anonymous.

This morning I tweeted:

“incredible how major news outlets take as fact what a single twitter user said about yesterday’s #GoDaddy attack.”

I followed up a few minutes later noting that “attack” wasn’t the right word:

“I should clarify re: GoDaddy — shouldn’t even use word “attack” yet, could be something else entirely”

Indeed, Go Daddy has now confirmed it was an internal issue. It wasn’t attacked. Here’s what the company had to say just moments ago:

Yesterday, GoDaddy.com and many of our customers experienced intermittent service outages starting shortly after 10 a.m. PDT. Service was fully restored by 4 p.m. PDT.

The service outage was not caused by external influences. It was not a “hack” and it was not a denial of service attack (DDoS). We have determined the service outage was due to a series of internal network events that corrupted router data tables. Once the issues were identified, we took corrective actions to restore services for our customers and GoDaddy.com. We have implemented measures to prevent this from occurring again.

So basically some guy with a Twitter account says he’s part of Anonymous and that he was responsible for the outage, and big publications took him at his word.

Sigh.

If you want someone to blame for the outage, apparently it’s Karl.

Comments

  1. says

    The big question is Godaddy trying to put a spin on this and say they didn’t have a DDOS? I think it’s funny that the problem was a corrupt router tables?

  2. Jason says

    I suppose it all depends what you believe (and what the people want to hear).

    Wouldn’t you rather hear that it was something internal rather than a security (or insecurity) hack/ddos attack on their network?

    It’s he said versus she said.

    They should have simply said something tripped over the hosting ethernet cord and called it a day.

    Either way, glad to see their back up and running.

    • says

      @ Jason – I think it would actually be better to say it was a ddos. And internal screwup means they have no one to blame but themselves.

      And I’ll believe Go Daddy over some anonymous twitter user any day

  3. Daniel Sydnes says

    Much of this speculation would have been unnecessary if GoDaddy proactively broadcast technical updates. Following their Twitter feed (https://twitter.com/GoDaddy) or contacting their tech support was an exercise in frustration.

    Contrast this with Amazon or Google — other large scale providers who provide a status monitor along with detailed analysis of failures:

    http://status.aws.amazon.com/
    http://aws.amazon.com/message/65648/
    https://aws.amazon.com/message/67457/

    http://www.google.com/appsstatus
    http://gmailblog.blogspot.com/2009/09/more-on-todays-gmail-issue.html
    http://gmailblog.blogspot.com/2011/02/gmail-back-soon-for-everyone.html

    If GoDaddy’s problems were internal, it should have been obvious when inspecting the flow rates on their peer routers and upstream providers.

    Bottom line, telling their clients, “We’re aware of the trouble,” just doesn’t cut it.

Leave a Reply