The post-incident stay-or-go checklist

The post-incident stay-or-go checklist
Heard this week: a multi-hour outage at a host that handled the comms worse than the outage. Before you decide to stay, score the response:
— Did the status page update during the event or after?
— Was there a real root-cause writeup or a 'we apologize for any inconvenience'?
— Did support acknowledge before customers had to ask?
— Were credits offered unprompted, or only to the loud?
— Has the same failure recurred since the last owner took over?
A source tells us how a host handles its worst day post-acquisition tells you everything about the next year.
Watch this: vague postmortems are the new resignation letter from the engineering team.