KiwiFlare

Been dealing with so many 429s and still am, but now the contentless pages have returned. No VPN, on desktop with only IPv4.
 
Been dealing with so many 429s and still am, but now the contentless pages have returned. No VPN, on desktop with only IPv4.
I have no information on how this happens. I don't know what people are doing to accomplish it.
 
I have no information on how this happens. I don't know what people are doing to accomplish it.
I can provide plenty details potentially relevant to the issue for you at a later time. The contentless pages aren't too big of a deal, it's the 429s that push me onto Tor.
As for now, about as much as I can think about is that I usually open a few watched threads in new tabs at a time, and usually a few of them will be blank out of the whole bunch. No idea what causes the 429s, I've gotten them and been unable to access KF for the next 15 minutes or just by loading the front page for the first time of the day. Funky stuff, no easy task.
 
  • Agree
Reactions: fake farts
Not troonbux. Tax payer bux.

You can bet your ass these freaks live on welfare just like the legendary anti-work reddit mod on Fox News.
So long as they receive any kind of social aid, they will always dedicate part of it to attacking this website until their tugboat runs out, the zeitgeist changes or the website actually falls.

Frankly, I am amazed Null didn't had a hitjob on him yet.

They have pull on banks, paypal, all relevant social media, cloudflare and FUCKING TIER 1 PROVIDERS!
You'd think that showing his face online would be enough for full scale weaponized autism to get him doxxed by now.

One x for doxing, not two.

The difference is Null lives in some third world hidey-hole, is paranoid and takes measures to prevent tracking (Faraday cage bags, destruction of all electronic devices to prevent tracking), hasn't had a recent picture in years, and doesn't have social media where he lays it out for the world to see.

I wouldn't be surprised if he had fake names. You think he'd give his real name and number to the local pizza guy?
 
We've been under near-constant D/DoS attacks for the last few days. The system has mostly been able to handle it with some config tweaks, but the net was cast too wide, which was causing 429 errors. I've identified the problem and you should no longer see 429 errors.

Just now, I applied a small update to the KiwiFlare which should have a big change. I believe I have improved the system's ability to handle concurrency. I had observed that the CPUs were not pegged (meaning, they were well below 100% utilization), but there was another bottleneck, which I believe was poor concurrency causing all 48 cores to block when receiving thousands of requests a second.

In my local tests, I had previously been able to cause DDoS loads of 30,000+ requests before seeing issues. However, with the new improvement, I was not able to reproduce the issue with any number of requests before being bottlenecked by socket counts.


Edit: There's a very heavy attack that I'm using to experiment with config options.

Please report if you receive an Error 403, or Error 429, while using the website.
I need to know if you are using a VPN or public network as well. If you are using a VPN, please say which one.
Good doggy, I thought i was the only one receiving these, glad i'm the only one who got pozzed like this.
 
Please report if you receive an Error 403, or Error 429, while using the website.
I need to know if you are using a VPN or public network as well. If you are using a VPN, please say which one.
Error 429, here. I am using the VPN service that comes with Norton 360 - and I had wondered if that was causing the errors. Glad to see you're on top of things, chief.
 
I have no information on how this happens. I don't know what people are doing to accomplish it.
Yesterday I got a few 429s (over the weekend got a couple 504s, a 502, and a short while when there was just no connect at all ("cannot find server")).

I was on my phone only, and run Proton VPN. For the 429s, disconnecting the VPN then reconnecting to a different server cleared the error right away. (In the past that hasn't always worked immediately, but it did yesterday.)

In sum, I could tell there were attacks going, but kiwiflare seems to have handled them well.
 
Intermittent 429 in chat over pia. Everything else seems good.
 
I'm on desktop, using FireFox, no VPN. I get a ton of 429s whenever I open links in new tabs. If I just stay on one tab and navigate the site that way, I don't seem to get 429 errors.

Yesterday the errors were happening constantly, today I've only gotten one or two.
 
We've been under near-constant D/DoS attacks for the last few days. The system has mostly been able to handle it with some config tweaks, but the net was cast too wide, which was causing 429 errors. I've identified the problem and you should no longer see 429 errors.
Very nice. It's handling it well. The mitigation is also having the semi-optimal result that instead of failing entirely, service simply slightly degrades. Daily dilation of stinkditch is pathetic.
 
Regular shitty american ISP, clearnet - has been working fine for the past hour or so. Good work null
 
Back