If cloudflarestatus.com isn't serving text content as Cache-Control: no-cache, that's itself an egregious bug.

It serves Cache-Control: max-age=0, private, must-revalidate. Same thing as far as I get it, maybe wider support.

Their status page is hosted on Cloudfront, perhaps adding an unintended caching layer.

Is it? From my end it looks like a plain ec2 instance from statuspage.io.

Cloudfront supports Cache-Control: no-cache

Cloudfront itself can cache the content regardless. (if its headers are showing HIT)

It might have been cached on the server but was not cached on my clients: I did a forced refresh and used a private browser window but it only showed the “almost everything is good” view throughout the duration of the incident.

The actual incident page was correct.

Can confirm that we had the same view. Operational while not working.

All I saw was a vague message at the top, all services were marked green and operational throughout.