Suggest subscribing on https://www.cloudflarestatus.com/ as that was updated long before I came to HN to say anything (which was only after the incident was resolved).

Maybe it happened because you're busy commenting on HN instead of checking their status page.

Aviate Navigate Communicate.

They did all three of those in the space of a few minutes (if you were checking their status page - which you can subscribe to by the way).

That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.

> That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.

I agree with you, but Cloudflare seem to have done exactly what you're describing in this instance?

Yes, my comment was about the Aviate Navigate Communicate rule, not about cloudflare's response