Latest news of the domain name industry

Recent Posts

Breaking: Go Daddy was not attacked

Kevin Murphy, September 11, 2012, 15:35:47 (UTC), Domain Registrars

Go Daddy’s outage last night was caused by an internal cock-up and not an attack.
The official line is that the downtime, which many reports had attributed to an Anonymous attack, was actually caused by “a series of internal network events that corrupted router data tables”.
The company, whose customers suffered from four to six hours of downtime yesterday, just issued the following statement:

Go Daddy Site Outage Investigation Completed
Yesterday, 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 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

I reported earlier today that the incident bore many of the hallmarks of a DDoS attack, but that’s clearly now proven to be incorrect.


Comments (2)

  1. Rubens Kuhl says:

    Corrupt router tables alone wouldn’t cause such an extended DNS outage. Lack of monitoring is required to achieve 6h of outage.

Add Your Comment