[156202] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Heads-Up: GoDaddy Broke the Interwebs...

daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Tue Sep 11 16:19:04 2012

From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <CAL9jLaa63A5q2gVkJF1zsyHZ3WFGcbkXm8WcM6bF5N93qpnfOg@mail.gmail.com>
Date: Tue, 11 Sep 2012 16:18:10 -0400
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Sep 11, 2012, at 16:04 , Christopher Morrow <morrowc.lists@gmail.com> =
wrote:
> On Tue, Sep 11, 2012 at 3:47 PM, Damian Menscher <damian@google.com> =
wrote:
>>=20
>> Summary: 30 minutes late on the start time, and off by well over an =
hour on
>> the stop time.
>=20
> even a broken clock is right 2x/day?
> nostrodamus was eventually right a few times?
> 'If you're cold, shoot until you get hot, then keep shooting!' - dick =
vitale
>=20
> folk like to look for the most complicated/spooky/crazy reason... most
> often it's just a simple reason for failure :(
> so far godaddy seems to agree with the 'it was a simple mistake on our
> part' (paraphrased, they probably won't say 'simple')

No large flows reported to the affected NSes, tweets were suspicious at =
best, other anon-ops denied the attack was them, and GoDaddy admitted =
internal error.

I'm going to take GoDaddy at their word, and give them major kudos for =
owning up to the mistake - in public.

--=20
TTFN,
patrick



home help back first fref pref prev next nref lref last post