Web hosting company and self-proclaimed world’s largest domain registrar GoDaddy suffered a major outage on Monday, taking down what’s believed to have been millions of websites. A hacker with the handle of AnonymousOwn3r claimed responsibility in a Twitter feed. The hacker is apparently not connected with Anonymous, one of whose Twitter feeds, YourAnonNews, urged readers to look to AnonymousOwn3r as the culprit. GoDaddy tweeted during the outage that it was aware of the “trouble” it was having and that it was working on the issue.
Yup. This from a group that accused me of simultaneously changing the DNS on 30 domains in my account and another 50 in another, of which I lost all 30 and they all 50 clients when those 80 address lost the connection to our servers (Oct 30th, 2010). The change time stamps on their end were all within 1 second of each other. There was no way on the planet that it could have been done by a human(s) as it was insisted it was and that it was all my fault. My accounts have been wiped and mysteriously reappeared with all the registration info changed, leaving me with hours of changing it back. ICANN was not happy about that. So . . . basically this "excuse" of theirs has no validity with me. It's just another GD "F" Up that they will try to pass off on anyone but themselves.
From my history with GD, it was internal, another "maintenance goof". With many more to look forward to. Stayed tuned.
Loading ...
GoDaddy Outage: Anonymous Attack or Maintenance Goof?
Posted by: Richard Adhikari September 11, 2012 11:48 AMWeb hosting company and self-proclaimed world’s largest domain registrar GoDaddy suffered a major outage on Monday, taking down what’s believed to have been millions of websites. A hacker with the handle of AnonymousOwn3r claimed responsibility in a Twitter feed. The hacker is apparently not connected with Anonymous, one of whose Twitter feeds, YourAnonNews, urged readers to look to AnonymousOwn3r as the culprit. GoDaddy tweeted during the outage that it was aware of the “trouble” it was having and that it was working on the issue.
From my history with GD, it was internal, another "maintenance goof". With many more to look forward to. Stayed tuned.