Cloudflare outage caused by botched blocking of phishing URL
-
For such a large org, they did not have 2-party review/approval for high risk changes prior to this incident. You’d think there would be at least review and approval before a change is implemented.
-
That's why I am not rellying on them for my slefhosting needs
-
Personally I think they have a much better track record of not making dumb mistakes than I do...
-
And yet, two typos in this sentence alone... I hope you're more careful about proofreading your configs.
-
From the blog post someone else linked, it sounds like they do have this process but it's just a process it's not enforced by their control software. So someone has made a change without following the process, and they mention prioritising getting enforcement into their control panel or whatever.
-
The number of these that their researchers receive it would be impractical.
-
Android keyboard, set up in french and I care less about random comments on Lemmy than in my configs. Also, this kind of typo would results in error, not unsafety
-
I guess mel isn't going to use you for their self hosting needs either, then.
-
I mean it's just eventual that shit like this will happen at that scale. As long as people are involved you really can't guard fully against it.
-
Ah another day, another Cloudflare cockup. It would be nice if the service that insists on MitM’ing a huge chunk of the internet could focus a bit more on stability.
-
As long as people are involved you really can't guard fully against it.
AI will save us.
