Heads-Up: GoDaddy Broke the Interwebs...
naveen at lastninja.net
Wed Sep 12 06:43:57 UTC 2012
> we do not know what happened. we have an apology, not an explanation or
> reasonable post mortem. all else is conjecturbation.
Agreed. And as Chris and Kyle pointed out, there is no indication
that the problems were present in the BGP DFT, and the issues could've
occured over iBGP. I completely concur with this, and do not preclude
it as an explanation.
But I would just like to put this out there.
In the past, GoDaddy has clashed with the Internet due to their
initial stance on SOPA, which resulted in a noticeable loss of
customers and generated a significant amount of bad press.
Now, there's a lot of conjecture as to what caused their outage.
But the most harm to GoDaddy would be reporting that they had a security
breach or DoS/DDoS attack which would instill fear in their customer base.
The major media outlets had already picked this up and started to report
foul play by Anonymous, denial of service attacks, or whatever.
To save face, it would make the most sense not to mention that a
security breach or DoS/DDoS attack occured. Indicating a security breach
would be immediate concern for any customer. If it was a DoS/DDoS attack,
they're basically admitting that they don't have an infrastructure capable
of withstanding or mitigating such attacks (which competitors such as
Cloudfare do claim). So the best option would be to spread disinformation
if either occured, and offer /generous/ service credit to earn back
customer goodwill and confidence.
This is simply why I remain skeptical. And as I said earlier, it would
be nice to receive more information of what actually happened, if GoDaddy,
or anyone in the know with GoDaddy, would oblige.
More information about the NANOG