What's interesting is that the !NANOG part of the universe presumes
the maintenance was to be performed by Twitter, not by their carrier
(i.e. server, not network, upgrades). Given the fact that the
WhaleFail has become a commonly-recognizable sight, I can see this
make people a bit, um, nervous. The real impact of the maintenance
would have most likely been minimal short of a Murphy strike.
That said, kudos to NTT for backing off in the face of some pretty
momentous current events, and hope the delay doesn't cause too many
ripple-effect problems for them.
-C
On Jun 16, 2009, at 10:48 AM, Jack Bates wrote:
Erik Fichtner wrote:
And yet, all upgrades can be postponed with the right... motivation.
Hmmm, you do know that motivation may have strictly been, "Your
maintenance corresponds with a major event, can you put it off for a
day?"
The maintenance in question has obviously been marked critical by
NTTA with what appears to be short notification and limiting the
delay to a minimum. They may have been unaware of the event and its
importance to their customers.
I'm more curious about what maintenance they are actually
performing. I know they run mixed Cisco/Juniper, and all their
Junipers should be able to handle in service upgrades. Of course,
even switching hits of an upgrade warrants setting a maintenance
window and notification due to Murphy.
Jack
