Home / Companies / Cloudflare / Blog / Post Details
Content Deep Dive

Cloudflare incident on November 14, 2024, resulting in lost logs

Blog post from Cloudflare

Post Details
Company
Date Published
Author
Jamie Herre, Tom Walwyn, Christian Endres, Gabriele Viglianisi, Mik Kocikowski, Rian van der Merwe
Word Count
1,644
Company Posts That Month
8
Language
English
Hacker News Points
9
Post removed?
No
Summary

The Cloudflare Logs incident on November 14, 2024, resulted in a significant loss of customer event logs due to misconfiguration and cascading failures within the system architecture. The incident highlighted the importance of subsystems protecting themselves from failures in other parts of the larger system to prevent cascades. A bug in the configuration system led to an initial mistake, which triggered a second latent bug in Logfwdr itself, causing a massive spike in customer logs being sent by the service. The subsequent overload on Buftee, a buffer management system, resulted in it becoming unresponsive and unable to handle the increased workload. The incident serves as a reminder that failures within systems at scale are inevitable and require proactive measures to prevent recurrences, including regular testing and configuration of fail-safes and backup systems.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 1 1,473 288 90 -20%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.