|
| Authored by: PJ on Tuesday, September 11 2012 @ 10:22 AM EDT |
That was my first thought. But that kind of
attack, I then thought, can happen to
anyone.[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Tuesday, September 11 2012 @ 10:42 AM EDT |
The Name Servers would not resolve. Could be something as simple as DDoS from
many bots using basic Linux dns test scripts. So far godaddy is quiet on the
exact method or flaw. Extremely hard to protect from DDoS but one can mitigate.
Points to a soft spot in godaddy.[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Tuesday, September 11 2012 @ 03:11 PM EDT |
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.
The service outage was not caused by external
influences. 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.
At no time was any customer data at risk or were any of our systems
compromised.
posted by user pwobbe, Tue Sep 11 2012, 17:47[TZ?] at
isc.sans.edu
[ Reply to This | Parent | # ]
|
- Tinfoil Hat says: - Authored by: Anonymous on Tuesday, September 11 2012 @ 03:24 PM EDT
- I'm likin this. - Authored by: Anonymous on Tuesday, September 11 2012 @ 03:40 PM EDT
|
|
| Authored by: Anonymous on Tuesday, September 11 2012 @ 04:41 PM EDT |
Of course, godaddy will not want to admit this. "corruption" in a
router table is "unusual" and usually points to a fundamental
misunderstanding of the issue.[ Reply to This | Parent | # ]
|
|
