April 7th, 2015

The details of the major incident were not clearly articulated, but whatever it is, it's already over

When a server is taken offline, be it a planned unplanned outage or an unplanned unplanned outage or something else, the operations team send out a series of messages alerting customers to the issue. Some time ago, I received a notification that went like this:

From: Adam Smith
Subject: Nosebleed Service : Major Incident Notification – Initial
Date: mm/dd/yyyy 1:16AM

Major Incident Notification

dfdsfsd

Affected Users

fdfsdfsdf

Start: mm/dd/yyyy 12:00AM Pacific Standard Time
mm/dd/yyyy 8:00AM UTC
End: No ETA at this time.

Incident Duration: 1 hour 15 minutes

Impact

fsdfdsfsdf

Continued Notifications

fdsfsdf

Information & Support

  • Other Support: Please send questions or feedback to

Thank you,

Adam Smith
IT Major Incident Management

Well that clears things up.

Curiously, the message includes an incident duration but doesn’t have an ETA. Thankfully, the message was sent one minute after the incident was over, so by the time I got it, everything was back to normal.

Topics
Other

Author

Raymond has been involved in the evolution of Windows for more than 30 years. In 2003, he began a Web site known as The Old New Thing which has grown in popularity far beyond his wildest imagination, a development which still gives him the heebie-jeebies. The Web site spawned a book, coincidentally also titled The Old New Thing (Addison Wesley 2007). He occasionally appears on the Windows Dev Docs Twitter account to tell stories which convey no useful information.

0 comments

Discussion are closed.