Slashdot Mirror
Go Daddy: Network Issues, Not Hacks Or DDoS, Caused Downtime
miller60 writes "GoDaddy says yesterday's downtime was caused by internal network problems that corrupted data in router tables. 'The service outage was not caused by external influences,' said Scott Wagner, Go Daddy's Interim CEO. 'It was not a 'hack' and it was not a denial of service attack (DDoS). ... At no time was any customer data at risk or were any of our systems compromised.' The outage lasted for at least six hours, and affected web sites and email for customers of the huge domain registrar."
... so the NSA could install their backdoors.
An enigma, wrapped in a riddle, shrouded in bacon and cheese
Wow, anonymous was so good they were undetectable... And they almost got away with it too. To bad anonymous caught them.
This just makes them look even less competent as a service provider, if the problem was purely internal then.
Then I've got a fully alive not dead elephant to sell you.
if they'd pay some of that massive advertising budget to competent employees, quality software and proper maintenance. ... naw, bring on the chick ads.
So that's, what, two big hits for Go Daddy this year?
A feeling of having made the same mistake before: Deja Foobar
Never attribute to malice what can be attributed to GoDaddy's incompetence just as easily.
Check out my sci-fi/humor trilogy at PatriotsBooks.
There was no other indication of a DDOS than the "I did it" tweet by a lone troll. To knock out someone as big as Godaddy for as long as they did would've required an epic-scale DDOS and you'd think something like that would've been noticed by their upstream providers.
This is the second time this week an Anonymous troll lied about an attack (the other one was stealing iPad device ID from FBI)... Anonymous's sterling reputation is being tarnished!
Hey, cut them some slack. Lying in public is one of the few pleasures of having a customer base that consists of people who don't know better...
Because someone on twitter said that they did it and everyone believed them?
Disclaimer: I work for a company that got "bought out" by KKR, just like GoDaddy.
Since KKR bought them out, GoDaddy has jacked up their prices (to make up for the billions I'm sure KKR "leveraged" out of GD for their execs and shareholders), took a pro-SOPA and PIPA stance (which garnered them a bit of a boycott), and is now having infrastructure problems. I haven't heard, but I'd bet there were layoffs and some brain-drain shortly after the KKR mafia took over.
Go figure.
If you own stock in a company that is being eyed by KKR (think: Bain Capital) dump it quick. If you're a customer, make plans to jump ship.
What's worse: Not being able to keep your network running when someone actively tries to disrupt it, or not being able to keep your network running under otherwise perfectly normal conditions?
The Tao of math: The numbers you can count are not the real numbers.
You would think so, but the company I work for uses GoDaddy (At least up until today we did, we may be going elsewhere now) for our registrar, but nothing else. We run our own DNS servers, our own web servers and load balancers, our own mail servers, etc. but we got scads of complaints about "the website is down" yesterday during the event. We traced it back to external DNS failures, but I have full-time monitoring on all of our systems and nothing on our end even hiccuped. It worked for some locations but not others.
It makes no sense to me either.
... And so it comes to this.
If one "anonymous" person could take down 5 million websites then we might as well give up on the Internets ...
Then again it could have been one GoDaddy Admin who accidentally misconfigured the routing tables that caused all of this ... I'd probably want to be anonymous if I was that person as well ...
They were down for 6 hours but still claim 99.999% uptime. But unless they have been around for more than 57 years, I dont' see how that is possible. Wonder what funky math they use to back up that number.
https://encrypted.google.com/search?q=5+hours+%2F+(1-99.999%25)
You sure it was not say a SSL issue with certs issues by them - they now are a CA as well. The crl is a crl.godaddy url -- depending on browser, if crl is not available then ssl can be flagged as invalid.
A registrar of a domain has NOTHING to do with the resolving of your domain, once it has been sent to roots.
Do a simple dig +trace query for your domains, where in that line would your registrar be talked too? You hit roots, you hit servers for your tld (org.com,etc), you hit your NS = done. A registrar does not come into play for the resolution of a fqdn - unless they are hosting your dns, or they host the site.
Now if godaddy was in line for resolution of your the domain your NS reside in, then ok that could cause some problems if they are down.
What are you hosting on your site? If say ADs or images from other domains dns or site was hosted by godaddy - that could cause some issues if site loading if parts of your page could not be resolved.
To this I say "so what"? When you have one primary job to do - respond to DNS requests for millions of domains that are registered through you - and you fail to do so, it's over. No matter what the root cause is, you caused *millions* of web sites to be unreachable for most people, for a period of time spanning hours. This is not "oops", this is catastrophic failure from a business perspective.
I can only hope that sufficient numbers of customers will be as offended, and seek more reliable solutions.
"Yesterday, GoDaddy.com and many of our customers experienced intermittent service outages starting shortly after 10 a.m. PDT. Service was fully restored by 4 p.m. PDT. "
http://www.godaddy.com/newscenter/release-view.aspx?news_item_id=410
Must be that new definition of the word "intermittent." The one roughly synonymous with "total."
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
Yes, I'm sure it wasn't an SSL issue. It was a straight DNS "Domain not found" problem.
However, thank you for the idea of looking up the secondary NS records. Turns out our .com's nameservers reside in our .net domain, which is handled by GoDaddy. I'm off to change those to our static IP addresses.
... And so it comes to this.
Wouldn't you rather the world think that you were hacked by some unbeatable magic hacking group, then your company went down due to your own ineptitude?