You are right if the facts are exactly as presented and there is nothing more to know. I would say we should ready between the lines here. Most postmortems are

You are right if the facts are exactly as presented and there is nothing more to know. I would say we should ready between the lines here. Most postmortems are marketing artefacts to some sense designed to reassure customers so taking them at face value is not really good idea, I have written and read enough to know that it is rarely ever the full story for variety of reasons. It is quite possible like you say they are playing fast and loose with config and they have systemic process risks as you point out. It is also possible that the issue is not just routine congestion i.e. it is symptom and not the root cause, and they are not talking about it in detail either to make the communication simple enough for non networking experts to understand, but has enough depth for technical folks to kind of follow along and reassure their managements that cloudflare has handle on it . It could also be revealing more may give their competitors some crucial information about their IP/architecture and they are calling it routine congestion to not reveal that. Lastly, all of the above are not mutually exclusive, it could be all of them in parts too.