Business Cloudflare down: Websites such as X not working amid technical problems with the internet - Should have used Kiwiflare

Cloudflare down: Websites such as X not working amid technical problems with the internet​

Andrew Griffin Tuesday 18 November 2025 11:58 GMT

Parts of the web appear to have stopped working amid a technical problem at Cloudflare.

Visitors to websites such as X, formerly known as Twitter, and film reviewing site Letterboxd saw an error message that indicated that Cloudflare problems meant that the page could not show.

Cloudflare is an internet infrastructure that offers many of the core technologies that power today’s online experiences. That includes tools that protect websites from cyber attacks and ensure that they stay online amid heavy traffic, for instance.

“Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers,” the company said in a new update. “Further detail will be provided as more information becomes available.”

Tracking website Down Detector, which monitors outage, was also hit by the technical problems itself. But when it loaded it showed a dramatic spike in problems.

Affected users saw a message indicating there was an “internal server error on Cloudflare’s network”. It asked users to “please try again in a few minutes”.
 
Última edición por un moderador:
Can Null (or someone with the know-how) talk a bit about the technical requirements of deploying a proof-of-work "CAPTCHA" protection (I presume in conjunction with a number of external gateways), as Null has done with KiwiFlare, versus just clicking a button to deploy Cloudflare?
Cloudflare is incredibly easy by comparison to deploy and you get the added benefit of protection against volumetric attacks whereas the PoW pages are really there to tell bots to lift a finger or fuck off. Finding a bunch of providers who don't care about constant DDoSing and bullshit reports is not a trivial task either, though Null has put together a tier list.

Solving challenges in browser is also stupid slow. KiwiFlare sometimes takes upwards of a minute on my phone whereas I can consistently solve it in less than a second using my shitty single threaded C# implementation.

PoWs sort of work since a lot of bots are downright retarded and shit themselves when they encounter the page. There are other bots that are running on hardware so slow it's impractical to try and solve the challenge. Cloudflare bot detection is just a never ending game of whack-a-mole and there's a lot of motivation to bypass it so there's a whole cottage industry of paid software and services for it.

Realistically if you end up a target of a motivated individual, no one singular thing is going to prevent them from being able to fuck your shit up. A PoW challenge is just one part of your defense.
 
Cloudflare goes down,
Half the internet goes down,
Matthew Prince goes down on trannies.
 
acjgcp.jpg
 
how fast would your C# implementation run on a browser through wasm? is your code private?
It's AGPLv3 + NIGGER licensed and available on GitHub

Basically a port of yats' firebird.

I don't know shit about web stuff so I have no idea how fast my implementation would be. Probably not very given you'd need some minimal .NET runtime so while it might be fast to execute, it'd take an eternity to download.
 
Just ran Firebird with his wrapper Phoenix and it consistently finished in less than a second.

Would be interesting if someone made a Tampermonkey script that implemented this fast solver for the browser for normal users to use.

Also, is it known if people have used these fast solvers to try and DDoS Kiwiflare? Because I've read about people attempting to DDoS this site on posts here
 
Solving challenges in browser is also stupid slow. KiwiFlare sometimes takes upwards of a minute on my phone
I've not seen that large a delta on my phone as compared to my desktop, like 3 seconds tops between the two.

Thanks for the info, that lined up with my impressions.
 
I've not seen that large a delta on my phone as compared to my desktop, like 3 seconds tops between the two.

Thanks for the info, that lined up with my impressions.
On my phone it's weird, sometimes it's 3 seconds, and sometimes it can be 30 seconds or more. But usually I get impatient and reload the page on my phone to get a different challenge and then it's usually instant.

On my desktop it is consistently between like 3-7 seconds though, not any more usually.
 
Also, is it known if people have used these fast solvers to try and DDoS Kiwiflare?
They have
 
Cloudflare down
Billions$ must burn

I'm really curious how much money did all these faggots lose during the downtime. Would Cloudflare be financially liable for that?
 
I was wondering why all my favourite drug dealing sites are not working lately. Thank you kiwifarms for always supplying me with news!
 
Incident report is live, tldr jeets couldn't do sql and wrote a query lacking a crucial where filter, then jeets couldn't do change management and rolled out an infrastructure change exposing extra data to said query, then finally jeets couldn't do rust so an unhandled exception exploded their entire rectums to smithereens.

Would be interesting if someone made a Tampermonkey script that implemented this fast solver for the browser for normal users to use.
Using the fastest available browser implementation by default is even more desirable. Competent attackers will use the fastest available implementation, so giving real users on real (often slow) hardware a slow implementation limits how high Jersh can raise the difficulty without inconveniencing eg mobile users. Probably not his priority right now, but if we know that the default implementation is slow (I haven't measured this myself) then there's good reason to improve it globally.
 
Based Hacker News distributing "kudos" for Cloudflare being "open and honest" about their incompetence.

Like when I hired Mexicans to replace the shingles on my roof and they stabbed me in the lung with a screwdriver and set my dog on fire. Kudos for explaining the situation afterwards, though! Kudos.

Kudos!
 
Atrás
Top Abajo