{"id":44293,"date":"2015-04-07T07:00:00","date_gmt":"2015-04-07T07:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2015\/04\/07\/the-details-of-the-major-incident-were-not-clearly-articulated-but-whatever-it-is-its-already-over\/"},"modified":"2015-04-07T07:00:00","modified_gmt":"2015-04-07T07:00:00","slug":"the-details-of-the-major-incident-were-not-clearly-articulated-but-whatever-it-is-its-already-over","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20150407-00\/?p=44293","title":{"rendered":"The details of the major incident were not clearly articulated, but whatever it is, it's already over"},"content":{"rendered":"

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

From<\/b>: Adam Smith
Subject<\/b>: Nosebleed Service : Major Incident Notification – Initial
Date<\/b>: mm\/dd\/yyyy 1:16AM <\/p>\n

Major Incident Notification<\/b> <\/p>\n

dfdsfsd <\/p>\n

Affected Users<\/b> <\/p>\n

fdfsdfsdf <\/p>\n\n\n\n
Start:<\/b><\/td>\nmm\/dd\/yyyy 12:00AM Pacific Standard Time
mm\/dd\/yyyy 8:00AM UTC <\/td>\n<\/tr>\n
End:<\/b><\/td>\nNo ETA at this time. <\/td>\n<\/tr>\n<\/table>\n

Incident Duration<\/b>: 1 hour 15 minutes <\/p>\n

Impact<\/b> <\/p>\n

fsdfdsfsdf <\/p>\n

Continued Notifications<\/b> <\/p>\n

fdsfsdf<\/a> <\/p>\n

Information & Support<\/b> <\/p>\n