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

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

Yesterday dozens (hundreds?) of “respectable” publications noted 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 stated regarding yesterday’s #GoDaddy attack.”

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

“I ought to 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 firm had to say just moments ago:

Yesterday, GoDaddy.com and many of our clients experienced intermittent service outages starting shortly following 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 clients and GoDaddy.com. We have implemented measures to prevent this from occurring again.

So basically some guy with a Twitter account states 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.