Technology

37800 readers

87 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Cloudflare Logs Suffer Critical Failure, Losing 55% of User Data (securityonline.info)

submitted 2 weeks ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Archived

It's not just Microsoft and Crowdstrike: Cloudflare, the internet infrastructure giant, experienced a major outage on November 14th, resulting in the irreversible loss of over half of its log data. The outage, which lasted for 3.5 hours, stemmed from a faulty software update that crippled the company’s log service, preventing it from delivering crucial data to customers.

Log services are essential for network operations, allowing businesses to analyze traffic patterns, troubleshoot issues, and detect malicious activity. Cloudflare’s log service, which processes massive volumes of data, relies on a tool called Logpush to package and deliver this information to customers.

However, an update to Logpush on November 14th contained a critical error. As Cloudflare explained in their incident report, the update failed to instruct auxiliary tools to forward the collected logs, leading to a situation where logs were gathered but never delivered. This data was subsequently erased from the cache, resulting in permanent loss.

“A misconfiguration in one part of the system caused a cascading overload in another part of the system, which was itself misconfigured. Had it been properly configured, it could have prevented the loss of logs,” Cloudflare stated in their report.

While engineers quickly identified the flaw and rolled back the update, this triggered a cascading failure. The system was flooded with an overwhelming influx of log data, including data from users who hadn’t even configured Logpush, further exacerbating the issue.

Cloudflare has issued an apology for the incident and the permanent loss of user data.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 79 points 2 weeks ago* (last edited 2 weeks ago)

During the roughly 3.5 hours that these services were impacted, about 55% of the logs we normally send to customers were not sent and were lost.

Bullshit ass headline. They only lost 55% of logs generated during a three and a half hour stretch. The headline makes it read like they lost 55% of all their logs ever.

Still a big deal, a lot can happen in 3.5 hours, but not as big as a deal as the headline makes out.