Slashdot Mirror

← Back to Stories (view on slashdot.org)

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

Posted by Soulskill on 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."

10 of 143 comments (clear)

  1. Doesn't Really Help by Anonymous Coward · · Score: 5, Insightful

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

    1. Re:Doesn't Really Help by caknuckle · · Score: 4, Insightful

      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.

    2. Re:Doesn't Really Help by Kaptain+Kruton · · Score: 5, Insightful

      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.

    3. Re:Doesn't Really Help by bill_mcgonigle · · Score: 4, Insightful


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

      And we already knew they were evil , so ....

      GoDaddy for Congress!

      (corporations are people, my friend)

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  2. If you believe that... by Rix · · Score: 2, Insightful

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

    1. Re:If you believe that... by Anonymous Coward · · Score: 2, Insightful

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

  3. That makes more sense by Spy+Handler · · Score: 5, Insightful

    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!

  4. Re:Go away GoDaddy by fuzzyfuzzyfungus · · Score: 3, Insightful

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

  5. Re:Lies by maxwell+demon · · Score: 3, Insightful

    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.
  6. Re:Wow by Anonymous Coward · · Score: 2, Insightful

    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.