So Godaddy.com Wasn’t Attacked But Why Did They Wait Almost 24 Hours Before Letting Anyone Know?

Godaddy.com announced a short time ago they were not attacked or hacked yesterday but had internal network issues which caused widespread outage to millions of customer’s sites, domain names and email accounts.

According to the statement, all services were restored by 4pm PDT.

So why did we first get word that there was no attack or hack especially when hundreds of major media stories were reporting the outage as due to an attack or hack?

In the case of millions of sites, email accounts and domain going down silence is not golden and the sooner customers and the public can be informed the better.

Godaddy is still trending on Twitter.

Here is the statement:

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.

At no time was any customer data at risk or were any of our systems compromised.

Throughout our history, we have provided 99.999% uptime in our DNS infrastructure.  This is the level our customers expect from us and the level we expect of ourselves. We have let our customers down and we know it.

We take our business and our customers’ businesses very seriously. We apologize to our customers for these events and thank them for their patience.

- Scott Wagner
Go Daddy Interim CEO

 

 

Comments

  1. Andrew Allemann says

    How long do companies usually take to say what happened? 24 hours seems really fast to me. Especially if it wasn’t a ddos, because they had to go figure out what it was.

  2. Michael H. Berkens says

    Andrew

    I would say it depends.

    If its a small company with a few clients they can take days and it might be OK but when you know there are hundreds of stories from major news organization claiming hacking or an attack, I think the company has a duty to refute that info sooner than later.

    If they didn’t come to the conclusion until 11am today that it wasn’t an attack and reported it as soon as they came to that conclusion then they did as well as they could, personally I think they knew by last night if it was an Attack/Hack or not

  3. Andrew Allemann says

    I’m sure they figured it out last night. They got all the sites up. Then they sent the announcement out at 8:30 am local time this morning.

    I don’t really see any reason they’d release the info that it wasn’t a ddos attack late last night.

    Just my take.

  4. says

    John Berryhill PERMALINK
    I would expect those in a position to figure what happened, and to fix it, probably had their hands full actually doing those things.

    Respectfully.
    First class Baloney!
    Are you saying all 3500 employees were busy ? to do a tweet, I think part of the first order of business is to “let your customer informed.”
    I don’t know what looks worse : being hacked? or having Corrupted Infrastructure? both are part of Security … what serious domainers consider # 1 priority.
    Collateral damage: 2 skeletons came up again : The Dead Elephant and SOPA.
    The news even made it to CNN not sure if the correct version has done so… the hacking did.

    Best
    Robert Fernandez.
    Domo

Join the Discussion