this post was submitted on 19 Nov 2025
492 points (98.8% liked)
memes
18078 readers
1962 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Cloudflare was a chain of unfortunate events.
The TLDR is, a permission change caused a poorly written SQL query (without a properly filtering 'where' clause) to return a lot more data than normal. That data is used by an automated script to generate configuration files for the proxy services, because of the large return the configuration files were larger than normal (roughly 2x the size).
The service that uses these configuration files has pre-allocated memory to hold the configuration files and the larger config file exceeded that size. This case, of having a file too large for the memory space, was improperly handled (ironically but not literally ironically, it was written in Rust) resulting in a thread panic which terminated the service and resulted in the 5xx errors.
So, it's more similar to the Crowdstrike crash (bad config file and poor error handling in a critical component).