Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
Network Security The Internet IT

Go Daddy: Network Issues, Not Hacks Or DDoS, Caused Downtime 143

Posted by Soulskill from the but-a-random-internet-person-said-otherwise dept.
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."
This discussion has been archived. No new comments can be posted.

Go Daddy: Network Issues, Not Hacks Or DDoS, Caused Downtime More

Go Daddy: Network Issues, Not Hacks Or DDoS, Caused Downtime

Comments Filter:

  • Had to Take the Network Down... (Score:4, Funny)

    by CanHasDIY ( 1672858 ) on Tuesday September 11, 2012 @01:35PM (#41303259) Homepage Journal
    ... so the NSA could install their backdoors.

  • anonymous U So haxor!!! (Score:4, Funny)

    by DeTech ( 2589785 ) on Tuesday September 11, 2012 @01:36PM (#41303293)
    Wow, anonymous was so good they were undetectable... And they almost got away with it too. To bad anonymous caught them.

  • Doesn't Really Help (Score:5, Insightful)

    by Anonymous Coward on Tuesday September 11, 2012 @01:37PM (#41303299)

    This just makes them look even less competent as a service provider, if the problem was purely internal then.

    • Re:Doesn't Really Help (Score:5, Funny)

      by dyingtolive ( 1393037 ) <{gro.erihrofton} {ta} {ttenra.darb}> on Tuesday September 11, 2012 @01:42PM (#41303391)
      Yup.

      "Good news everyone, we weren't compromised. We're just incompetent!"

    • Re:Doesn't Really Help (Score:4, Interesting)

      by AlienSexist ( 686923 ) on Tuesday September 11, 2012 @01:44PM (#41303431)
      One way to be sure... hit em' again!

    • This just makes them look even less competent as a service provider, if the problem was purely internal then.

      Or if it turns out it was a hacker, that won't inspire confidence in GoDaddy either.

    • Re: (Score:3)

      by pspahn ( 1175617 )
      Or possibly a way for them to market their own Premium DNS offerings. I understand that users on Premium DNS were hardly affected (according to a co-worker who was monitoring the whole thing yesterday and had a number of Premium DNS users).

      • Or possibly a way for them to market their own Premium DNS offerings. I understand that users on Premium DNS were hardly affected (according to a co-worker who was monitoring the whole thing yesterday and had a number of Premium DNS users).

        Odd. I saw the reverse: our company's domain which is on GoDaddy's Premium DNS servers was affected, while a colleage's personal domain on the standard DNS servers was unaffected.

      • It's not that their premium DNS server is all that robust.

        You just can't have secondary slave DNS servers without it...

    • Re: (Score:3)

      by fermion ( 181285 )
      I commend them for being hones with their mistake. As an alleged premier top level domain name reseller, though, we would expect that they had the facilities to prevent both internal errors and external attacks. If I were superstitious, I would say something in the Juju right now. Lots of computer stuff going down.

    • Re:Doesn't Really Help (Score:4, Insightful)

      by caknuckle ( 2521404 ) on Tuesday September 11, 2012 @02:06PM (#41303811)

      This just makes them look even less competent as a service provider, if the problem was purely internal then.

      It might make them look less competent, but on the flip side suggests an "isolated" incident, and that it won't likely happen again, whereas if it's hackers you as a customer may wonder when the next hack will happen and what effect it will have on your websites, DNS etc. I.e. we better move off before it gets targeted again.

    • Re:Doesn't Really Help (Score:5, Insightful)

      by Kaptain Kruton ( 854928 ) on Tuesday September 11, 2012 @02:31PM (#41304199)

      It makes GoDaddy appear incompetent to geeks and computer-savvy users. However, to the average person that does not know much about computers, they will accept it as a computer problem that 'just happens'.... just like all of the errors that they have on their home computers that supposedly have no cause. As long as GoDaddy makes the problem sound really technical while saying they know exactly what caused it and know how to quickly implement a solution that prevents future instances, they will appear competent to the average computer user. After all, to an average user, an admin's ability to solve a problem that sounds complex will make the admin's skill sound really impressive.

      Remember many of GoDaddy's customers are individuals and small businesses that have mediocre computer skills that rely on a simplified WYSIWYG tool. To them, evil hackers that steal information are much worse than an annoying problem that just happens because computers all have problems (in their experience). As long as the customer doesn't realize that it was a problem that should not have occurred and it was only caused by incompetence, then they are less likely to lose those customers.

    • Sure, like Amazon or Microsoft hasn't had internal infrastructure issues either. Mistakes happen, things get overlocked, and then fixed. I am more interested in what their lessons learned were and what they have done to prevent a similar incident in the future.

  • If you believe that... (Score:3, Insightful)

    by Rix ( 54095 ) on Tuesday September 11, 2012 @01:37PM (#41303303)

    Then I've got a fully alive not dead elephant to sell you.

    • Re: (Score:2, Insightful)

      by Anonymous Coward

      How does it help GoDaddy to tell everyone that they are incompetent instead of admitting they were attacked?

      • Re: (Score:1)

        by Rix ( 54095 )

        If they were successfully attacked then their both incompetent and insecure.

    • Re: (Score:2)

      by rs79 ( 71822 )

      http://rs79.vrx.net/works/photoessays/2011/godaddy/ [vrx.net]

      Bob makes his own dead pachyderms.

  • Talk about having a bad day at the office... can you imagine being a Sys Admin at GoDaddy?

    We have a few odd DNS entries still hosted at GoDaddy. We'll be yanking those last ones away. Any advice on how to set it up so I'm not depending on one registrar?

    • Any advice on how to set it up so I'm not depending on one registrar?

      Yes. You can depend on more hosting services which use different upstream providers and are located in different datacenters. And pray they don't go offline in the same time :)

      • Re: (Score:2)

        by kwalker ( 1383 )

        That doesn't get around your registrar going down, just your hosting.

        • Thanks. I was trying to figure out how cnastase's solution was helping.

  • Perhaps... (Score:5, Interesting)

    by ackthpt ( 218170 ) on Tuesday September 11, 2012 @01:39PM (#41303333) Homepage Journal

    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?

  • I don't buy this for a nickel, and I doubt they are even capable of detecting that a problem was caused by "external influences".
    Laughably feeble attempt to save face in front of countless customers who should have known better than to use GoDaddy services.

    • Re:Go away GoDaddy (Score:4, Insightful)

      by fuzzyfuzzyfungus ( 1223518 ) on Tuesday September 11, 2012 @01:46PM (#41303467) Journal

      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...

  • Not so sure (Score:1)

    by Anonymous Coward

    I received emails last night from some SAAS companies claiming that there service outages were due to attacks by hackers. They did not mention GoDaddy specifically, but I know their DNS is hosted there.

    Why would they be saying it was hackers?

    Sounds like damage control to me.

    • Re: (Score:2, Informative)

      by Anonymous Coward

      Because someone on twitter said that they did it and everyone believed them?

  • That makes more sense (Score:5, Insightful)

    by Spy Handler ( 822350 ) on Tuesday September 11, 2012 @01:44PM (#41303443) Homepage Journal

    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!

    • Re: (Score:1)

      by Anonymous Coward

      I like how you so easily believe that they were both false. It makes me giggle.

      • We have one Anonymous member claiming that it was his attack that brought down GoDaddy.
        We have GoDaddy claiming that it was network issues.

        Lacking any further evidence, we're in a he said-she said scenario. While I'm not advocating blindly believing GoDaddy representatives, blindly believing an Anonymous member without any evidence to back him up seems foolish also. (A tweet the Anonymous member made during some service's downtime doesn't count as evidence.)

    • Re: (Score:1)

      by Anonymous Coward

      What I think you mean is anonymous troll. Anonymous weren't trolling, as in, a person who is an active participant in the Anonymous movement.

      There is a difference between an anonymous person and an Anonymous person in this case. The former is just any random person on the internet with a pseudonym trying to troll the latter, which is a group united under one pseudonym.

      • What I think you mean is anonymous troll. Anonymous weren't trolling, as in, a person who is an active participant in the Anonymous movement.

        There is a difference between an anonymous person and an Anonymous person in this case. The former is just any random person on the internet with a pseudonym trying to troll the latter, which is a group united under one pseudonym.

        Maybe you ought to trademark the term "Anonymous" - too many people are using it, customers get confused.

    • Then again at least they're honest enough to admit it, but then again the tweet only says, #TangoDown -- godaddy.com | by @AnonymousOwn3r. it appears to be the ASSumption of the original author that it was a DDoS.

      but then again taking a look at some of the tweets, you get more of a "c'mon are we actually taking this seriously?"

      Surely we can take some artistic Licences with the quotes from go-daddy as well! (From the article)
      Wagner also noted that the company has provided a 99.999 percent uptime in its D
    • Early in the outage (1st hr), I was looking at http://www.isitdownrightnow.com/godaddy.com.html [isitdownrightnow.com] and it was able to still ping godaddy.com (I'm assuming the IP was still cached), but it had, as I remember, 3000ms+ ping times. To me, this lends a little credence to the DDOS claims, but it is not definitive.

    • Re: (Score:2)

      by nmos ( 25822 )

      What makes you think an attack would have to involve a DDOS? There are other ways of attacking a network you know.

    • Re: (Score:1)

      by flex941 ( 521675 )
      Just yesterday I was cleaning up a customer's hacked Joomla site heavily pounding with pings and port 80 requests some North-American IP address. A bit later the GoDaddy DDOS news appeared on Slashdot. Coincidence?
  • This shirt [google.com] by Think Geek fits.
  • If you were hacked? It shows your defenses are weak.
    If you weren't hacked? It shows you have some seriously poor management/backup equipment.
    Either way, less people are going to want to use you after this.

  • Another KKR debacle (Score:2, Informative)

    by Anonymous Coward

    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

    • according to www.stockchase.com KKR

      "Would characterize dividend as not being safe because it is merely a function of income that the company generates on a quarterly basis. It goes up and down depending on whether they are capitalizing any deals. This quarter will probably have a very nice dividend because they just sold a position in Alliance Boots to Walgreens. Trades at a very reasonable price."

      In other news godaddy is still having problems. They weren't relaying emails from a website I have with them, I

    • If you own stock in a company that is being eyed by KKR (think: Bain Capital) dump it quick.

      Why would you dump stock of a take-over target? Just keep it until the take-over at least... stocks usually rise in anticipation of take-over, because the buyer, no matter how incompetent, will usually pay premium for the stock in order to ensure a quick conclusion of take-over... and if the buyer is so incompetent that he doesn't know that he has to do that, he won't be in a position to ruin the company, because he'll never own enough shares in it.

  • Well duh ... (Score:4, Funny)

    by jest3r ( 458429 ) on Tuesday September 11, 2012 @02:09PM (#41303861)

    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 ...

  • That's what it cost me to figure out that each hosted domain has a different credit card record for autorenewal. So updating one record won't stop the rest of your domains from expiring. Bastards. They're worse than Comcast.

    Good for me, though, since that caused me to switch everything to a competitor and not be affected by this outage.
  • This is almost certainly a result of a network change plus some really bad luck. Big player BGP peering connections are under intense scrutiny right now because of a few mistakes made at company A were introducing blackhole routes into company B (c,d,e,f's) routers.

    Networking is the most often overlooked, often shit on, everyday service that everyone ab(uses) and gets pissed when it doesn't work properly. Like toilets.

  • 99.999% Doesn't mean what you think it means (Score:4, Informative)

    by Anonymous Coward on Tuesday September 11, 2012 @02:19PM (#41304017)

    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)

  • So what? (Score:3)

    by thePowerOfGrayskull ( 905905 ) <marc,paradise&gmail,com> on Tuesday September 11, 2012 @02:39PM (#41304301) Homepage Journal

    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.

  • Intermittent (Score:3)

    by Spazmania ( 174582 ) on Tuesday September 11, 2012 @04:19PM (#41305615) Homepage

    "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 [godaddy.com]

    Must be that new definition of the word "intermittent." The one roughly synonymous with "total."

  • What if the cause was actually a hack, but they didn't notice it? Corrupted routing tables don't occur all by themselves and single routing tables taking a whole provider down doesn't happen that often either. I wouldn't rule out the possibility of *a* hack just jet.
  • 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?
  • So anonymous took responsibility for it? Wow, I guess they were talking out their asses just like any other immature, pathetic little hacker kid. Way to downgrade their image straight down the toilet.

Slashdot Top Deals

A computer lets you make more mistakes faster than any other invention, with the possible exceptions of handguns and Tequilla. -- Mitch Ratcliffe

Close