5 ms·
Are you sure it wasn't cached? For us it was showing correctly the incident...
by Heliosmaster 7y ago
Are you sure it wasn't cached? For us it was showing correctly the incident...
- wepower_ico 7y agoCan confirm that we had the same view. Operational while not working.
- grey-area 7y agoAll I saw was a vague message at the top, all services were marked green and operational throughout.
- btown 7y agoIf cloudflarestatus.com isn't serving text content as Cache-Control: no-cache, that's itself an egregious bug.
- grenoire 7y agoIt serves Cache-Control: max-age=0, private, must-revalidate. Same thing as far as I get it, maybe wider support.
- buildbuildbuild 7y agoTheir status page is hosted on Cloudfront, perhaps adding an unintended caching layer.
- auscompgeek 7y agoIs it? From my end it looks like a plain ec2 instance from statuspage.io.
- jmngomes 7y agoCloudfront supports Cache-Control: no-cache
- buildbuildbuild 7y agoCloudfront itself can cache the content regardless. (if its headers are showing HIT)
- acdha 7y agoIt 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.