[115728] in North American Network Operators' Group

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

Re: Re: Using twitter as an outage notification (was : Fire, Power

daemon@ATHENA.MIT.EDU (Brandon Galbraith)
Tue Jul 7 16:29:24 2009

In-Reply-To: <alpine.DEB.1.10.0907072220090.15149@uplift.swm.pp.se>
Date: Tue, 7 Jul 2009 15:28:33 -0500
From: Brandon Galbraith <brandon.galbraith@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: NANOG list <nanog@merit.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Tue, Jul 7, 2009 at 3:24 PM, Mikael Abrahamsson<swmike@swm.pp.se> wrote:
> On Tue, 7 Jul 2009, Marshall Eubanks wrote:
>
>> In a real crisis, redundancy rules.
>
> ... and simplicity.
>
> It's always "fun" when those outages pages rely on sql backends etc, so
> they're capable of tens or hundreds of users, so they look fine normally.
> When an outage happens and people really need the information and want it,
> things stop working.
>
> I've been advocating a distributed system with static HTML pages being
> generated and pushed out when things change. Huge load capability, you can
> put it anycasted at multiple IXes so it's geographically and ISP
resiliant,
> larger ISPs can even request to get their own mirror. Keeping it simple.
>
> No takers yet though, people seem to have too much confidence in
> complicated, centralized, nice looking solutions.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
>

http://www.coralcdn.org/

-- 
Brandon Galbraith
Mobile: 630.400.6992

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