[119029] in North American Network Operators' Group

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

Re: HE.net, Fremont-2 outage?

daemon@ATHENA.MIT.EDU (Scott Howard)
Wed Nov 4 19:32:23 2009

In-Reply-To: <200911042256.nA4MuJ1X031635@aurora.sol.net>
Date: Wed, 4 Nov 2009 16:31:28 -0800
From: Scott Howard <scott@doc.net.au>
To: Joe Greco <jgreco@ns.sol.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Wed, Nov 4, 2009 at 2:56 PM, Joe Greco <jgreco@ns.sol.net> wrote:

> > Yup, just ask 365 Main how reliable they are -
> > http://365main.com/status_update.html
>
> I would point out that my cursory review of the document linked above
> leaves a very positive impression.  I don't know the actual details well
> enough to know if there is any reason to doubt the document...
>
> I would, however, tend to trust a vendor who disclosed events in this
> manner.  Even the best systems can fail.  How a failure is handled is
> in many ways the more important factor; being transparent about it is
> good for confidence.
>

Absolutely!  365 Main handled this outage very well, both at the time, but
more importantly with the followup as you can see from the URL above, which
as you can see was made (very!) public by them at the time, and not covered
in "confidential/customer only/etc" warnings.

Those that have (finally) received the notification from HE about yesterdays
outage will notice the stark difference between the way they've handled it
and the way 365 Main handled things...

  Scott.

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