GoDaddy: We Were Not Hacked!

Updated on

GoDaddy, the Domain Names System (DNS) hosting and registrar company, has denied an anonymous user’s claim that yesterday’s outage was due to hacking.  Some of company’s associated websites (DNS registerd/hosted) went offline yesterday at about 10.25 a.m, and was restored at around 2.43 p.m for a majority of its customers, as mentioned in earlier posts today.

GoDaddy: We Were Not Hacked!

Yesterday, an anonymous user under twitter account @AnonymousOwn3r, had tweeted #TangoDown – godaddy.com, later claiming credit for the outage experienced by millions of customers worldwide. The person later received some serious replies, from people unhappy with his activity, as covered in our previous article, but now it appears his claims were nothing more than a bluff.

The company’s CEO has come out in the open in what appears to be ‘a clear the air statement.The service outage was not caused by external influences,” the company’s interim CEO, Scott Wagner, said in a statement. “It was not a ‘hack’ and it was not a denial of service attack (DDoS),” CNET News noted.

Additionally, the CEO echoed remarkes earlier communicated by the company’s vice president of public relations, Elizabeth Driscoll, saying, “no time was any customer data at risk or were any of our systems compromised.”

Wagner was also very apologetic to the affected customers in thanking them for their patience, despite having temporarily redirected all DNS activity to a peer company, VeriSign, Inc. (NASDAQ:VRSN), which was overseeing the execution of the various requests during the blackout period.

The company also said that the outage was due to internal causes, albeit without giving clear specifications in a statement. Godaddy states:

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.

We will keep you updated on further developments on the issue as they unfold.

Leave a Comment