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