Looks like this time they first considered that they screwed up themselves, unlike the last time when they were fighting a phantom attack for a while until they realized that it was their own fault.
If all you use them for
is caching, then they could provide webhooks for their scheduled maintenance so customers can disable cloudflare during the maintenance and reenable it once it's all good.
However, for customers using other things, perhaps we need an independent cloudflare for cloudflare service that serves its own cache of your site when cloudflare is inaccessible.
Could combine the two ideas so when there is scheduled cloudflare maintenance, it switches dns to the cloudflare for cloudflare service that uses cloudflare if online but if cloudflare is offline then serves cache, and once cloudflare maintenance is finished then restore cloudflare dns.
25 comments
[ 2.1 ms ] story [ 36.9 ms ] threadYou are the future of the operational internet!
While down times are not ideal, that's quite an impressive achievement to be able to resolve an incident of this scale in minutes - not hours.
[0]: https://updog.ai/status/cloudflare
However, for customers using other things, perhaps we need an independent cloudflare for cloudflare service that serves its own cache of your site when cloudflare is inaccessible.
Could combine the two ideas so when there is scheduled cloudflare maintenance, it switches dns to the cloudflare for cloudflare service that uses cloudflare if online but if cloudflare is offline then serves cache, and once cloudflare maintenance is finished then restore cloudflare dns.
Plex, Plexamp, and accounts in Sonos went down.