Go Daddy: Network Issues, Not Hackers or DDoS, Caused Outage
September 11th, 2012 By: Rich Miller
Go Daddy says yesterday’s downtime, which caused extensive downtime for customers, was caused by corrupted data in router tables, rather than an external attack or hack. Routing tables include a database of information about network destinations.
Many media outlets attributed the downtime to an electronic attack, based on Twitter postings.
“The service outage was not caused by external influences,” said Scott Wagner, Go Daddy’d Interim CEO. “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 customers and GoDaddy.com. We have implemented measures to prevent this from occurring again.”
Wagner said the outage lasted six hours, with the services being interrupted beginning at 10 a.m. PT and being fully restored about 4 p.m. PT. The outage was widely felt because of the huge scope of Go Daddy’s business. The company hosts 5 million web sites and manages a total of 52 million domain names.
“Throughout our history, we have provided 99.999% uptime in our DNS infrastructure,” said Wagner. “This is the level our customers expect from us and the level we expect of ourselves. We have let our customers down and we know it. We take our business and our customers’ businesses very seriously. We apologize to our customers for these events and thank them for their patience.”
Hank YeomansPosted September 11th, 2012
Routing tables do not include DNS information. DNS servers and Routers which route traffic from here to there are two different systems.
KylePosted September 11th, 2012
“Routing tables include a database of information about IP addresses and domain names, helping direct Internet users to the web sites they are requesting.”
This doesn’t make sense. A routing table could be corrupted and cause their DNS infrastructure to be unreachable but the saying that the router itself has a table mapping domain names to ip addresses is almost certainly incorrect.
Kyle and Hank: Yes, you’re right about this. We’ve removed that reference and included a link out to the Wikipedia entry. If there are better explainers/resources to link to, feel free to suggest them.
MauroPosted September 12th, 2012
Do thay have just one router?
Ah, costs cut
SaeedPosted September 12th, 2012
I think at this stage not CEO tell the whole story, the most technical person will cover this all things and tell us the actual situation with the Godaddy.
I am fully confident, the actual issue is something different as the CEO stupidly cover the story.
BobPosted September 12th, 2012
Anyone know of a router that has a table of domain names? Who wrote this?
DNS table/cache != Routing table…
GaryPosted September 12th, 2012
It is quite possible that a software bug could cause routing table corruption, human error can do the same thing. Once the error is introduced in one router, it can easily be propagated to others. It would not affect the DNS entries, but if the routers do not allow the outside users to reach the DNS servers, then you get exactly what we saw. The only question I have is how come it took 6 hours to debug that simple and common problem!!!
BlakePosted September 15th, 2012
Bullshit. Something broke or something wasnt tested properly in the event of a failure.
dns has nothing to do with routing.