Day-long outage 'not a hack,' claims GoDaddy Domain registrar GoDaddy has commented on the daylong DNS outage that downed many of its customers' websites on Monday, saying that not only was a hacker not responsible, but that the service interruption wasn't the result of a DDoS attack at all. "The service outage was not caused by external influences," Scott Wagner, the …
You'd rather issue a mea culpa and an apology for screwing up, than say a bully came along and kicked your ass, but you're going to boxing classes to make sure it doesn't happen again? Metaphorically speaking, of course, since judging by your past comments you're thick enough to need it pointed out.
Well, I've never been a custo^H^H^H^H^H victim of GoDaddy, but from all the complaints I've seen over the years, they must be the world's only ISP with a credibility rating in negative numbers.
While I'm not at all convinced that the Anon. claimant is telling the truth, I'm even less convinced that the outage was not the result of some form of crack.
Taken for face value, remember that it wasn't Anonymous who took credit for the outage, but rather an individual who identifies with Anonymous. More of the "lone wolf," if you will.
With everything going on, there could be a number of lies and trolling happening right now so none of us can really speak with authority on what transpired.
Paris, speaking without authority.
According to my source*, the cause of the outage was a mis-communication with the IT dept., which had been outsourced to an Indian company, which had outsourced the contract to the Phillipines, which had outsourced the contract to Slovenia, which had outsourced the contract to Mexico, which, in turn, had outsourced the contract to 8 year old Billy Waterspoon of England, who currently isn't allowed to use the computer because he was fighting with his sister.
Go Daddy expects all services back to normal by Friday, when Billy's punishment is over, unless it's extended because Billy won't eat his greens.
*Pulled from my ass.
I do not use GoDaddy DNS services. I have a virtual server hosted with them and that one could not be reached by it's IP address during the problem. This was clearly something else than just the DNS service being down since traceroute or ping to my IP did not work.
The 10 year old script kiddie who took "credit" probably thought his downloaded scripts did the damage.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
