Dev1 Galaxy Forum / Trying to explain what happened with Cloudflare?

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (zapper) — Fri, 05 Dec 2025 14:15:38 +0000

@blackhole, pretty sure if they below 5, they are mostly irrelevant, but if they above 7 they are a huge problem hence why I asked the severity of the vulnerabilities.

Although, I suppose their stability method could also have security problems.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (Altoid) — Fri, 05 Dec 2025 10:34:06 +0000

Hello:

I wrote:

... only one word was needed: ineptitude.

And it seems to be a gift that keeps on giving ...

The Register wrote:

Cloudflare suffers second outage in as many months during routine maintenance
The Reg is still standing (this time) despite our best efforts
by Richard Speed - Fri 5 Dec 2025 // 10:16 UTC

https://www.theregister.com/2025/12/05/ … age_again/

Best,

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (Gnostic) — Fri, 05 Dec 2025 10:15:24 +0000

We are still trying to teach our developers ideas and methods for resilient systems design. Simple things like having more than just Cloudflare as the DNS resolver. They looked puzzled last time, one even asked "Why would you need that?".

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (blackhole) — Thu, 04 Dec 2025 17:55:13 +0000

You can drill down to get that info. My point is that, Debian is actually not this pinnacle of design and engineering that some believe it to be. It's the approach of freezing at these specific package versions and then patching, that creates many of these problems, then the backporting of "upstream" security patches to older versions has been shown to be unreliable time and again - i.e. those patching not understanding what they're patching, and not factoring in upstream changes in newer versions and their dependencies which could render the patch useless or detrimental (it has happened).Then there are the plethora of bugs which remain unfixed for the lifecycle of a release, because they either can't be easily fixed without upgrading components to newer versions or there is no one willing/able to do the work.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (zapper) — Thu, 04 Dec 2025 06:12:17 +0000

blackhole what is the severity of those bugs though... how high are they rated? like 1-10

I meant debian because its known for stability. Not the security aspect lol.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (greenjeans) — Tue, 02 Dec 2025 19:38:51 +0000

Lol, not really that complex.

DuckDuckGo search terms: does cloudflare use ai to write code?

The answer at the top from the Duck's "search assist" (more ai, lol) :

Yes, Cloudflare uses AI models, such as Claude, to assist in writing code, particularly for projects like their OAuth library, where the AI-generated code is thoroughly reviewed by engineers for security and compliance. This approach allows for efficient coding while maintaining high standards of quality and safety.

Thoroughly reviewed bro...totally no hallucinating this time I swear...just push it, what's the worst that could happen bro?

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (blackhole) — Tue, 02 Dec 2025 18:19:54 +0000

"I thought the web was built more like Debian"

Lets hope not:

https://www.cvedetails.com/vendor/23/
https://www.cvedetails.com/version-list … Linux.html

Also:

https://security-tracker.debian.org/tra … ase/stable
https://bugs.debian.org/release-critica … n/all.html

FreeBSD for comparison

https://www.cvedetails.com/version-list … eebsd.html

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (kaiyel) — Tue, 02 Dec 2025 17:53:18 +0000

In retrospect perhaps our "technology leaders" should not have taken the decentralized network we call the Internet and centralized the crap out of it. But will we have learned from this? Doubt it.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (zapper) — Fri, 28 Nov 2025 01:50:03 +0000

One line of code caused all that?

I thought the web was built more like debian, not archlinux LOL.

I once made one tiny mistake in mkinitcpio.conf in Hyperbola and it wouldn't boot it dropped me to a shell.

The issue?

I didn't remove the parentheses from the i915 line

And therefore, I kept getting it borked every time I tried. lol.

This feels like that kind of situation.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (spliskin) — Tue, 25 Nov 2025 13:03:31 +0000

Good write-up, up front. Wish I could read the whole thing.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (Gnostic) — Tue, 25 Nov 2025 12:41:50 +0000

More RUST in the wheels of the internet.

On November 18, 2025, a significant portion of the internet went offline. X, ChatGPT, Canva, Letterboxd, and countless other services became inaccessible. The culprit? A single unwrap() call in Rust code that panicked across Cloudflare’s 330+ datacenters.

https://lucisqr.substack.com/p/the-clou … d-the-rust

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (spliskin) — Tue, 25 Nov 2025 08:46:05 +0000

Cloudflare - louded as one of the top developers in certain circles, should have known better than to release it so early without full vetting.

Nobody follows proper development cycles anymore either way. Knowing if a service of yours goes down it can cause that much trouble should inform you to be a more stringent and have hard policy as to production rollouts.

It's why I don't and won't work for them, that and their sales tactics; netflix as well. It's the reason I get annoyed when people complain about alternatives and still fail to realize that it's very difficult to replace things without some funding.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (Altoid) — Tue, 25 Nov 2025 05:57:30 +0000

Hello:

Gnostic wrote:

... picture is worth a thousand words.

Yes.

But only one word was needed: ineptitude.

Cloudfare is arguably an essential part of the web these days.
And those behind it (should) know it. Recent events make me wonder.

Whether that is the proper way to do things or not is for another discussion altogether.
But, like it or not, it is a fact: Cloudfare is a weak link without the needed redundancy.

Redundancy that the WWW was supposed to have, by design.
So it boils down to basic common sense: you do not fuck around with an essential part of the web.

Which is exactly what these DHs did.

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (zapper) — Tue, 25 Nov 2025 03:46:48 +0000

@spliskin

Makes sense

Re: Trying to explain what happened with Cloudflare?

dummy@example.com (stargate-sg1-cheyenne-mtn) — Fri, 21 Nov 2025 14:56:57 +0000

https://xkcd.com/2347/