13 ms·
After the release got reverted, it took an 1hr28min for the deployment to propagate. You'd think that would be a very long time for CloudFlare infrastructure.
by therein 9mo ago
After the release got reverted, it took an 1hr28min for the deployment to propagate. You'd think that would be a very long time for CloudFlare infrastructure.
- steve1977 9mo agoThey had to update all the down detectors first.
- tuetuopay 9mo agoGiven the seriousness of outages they make with instant worldwide deploys, I’m glad they took it calmly.
- rhplus 9mo agoWe should probably all be glad that CloudFlare doesn't have the ability to update its entire global fleet any faster than 1h 28m, even if it’s a rollback operation. Any change to a global service like that, even a rollback (or data deployment or config change), should be released to a subset of the fleet first, monitored, and then rolled out progressively.