Thanks for your support examplens.

Attack has slowed, but looks to be increasing again


They are attacking basically the api. All attacks go to bitcoindata.science/api/.....

---

On another topic, I have updated the balance checker tool, so it supports QR Codes now.



https://bitcoindata.science/bitcoin-balance-check

This was a Hhampuz request, and I think it is very useful



Maybe examplens is right, and cloudflare is attacking so I get a paid plan.

I guarantee that it is not up to the hosting provider in this case. 
Other sites (hosted with bitmover's site) do not have this problem, and from 01.01.2024 it is on a slightly more expensive package.


@bitmover, it looks like you messed up FeeBuddy with more aggressive settings on CloudFlare. I didn't see any posts from that side today.

I happened to think the same.

I don't know how you are managing the server, bitmover. But, I think you need to review this hosting company, as it could be a company that attracts these types of attacks.

Review your API code to check if there is anything that could be attracting the attention of these bots.

Where I live, when communism ended, insurance companies offered to protect and insure you against their own henchmen when you had a business lol
I think that's exactly what CF is doing in our case, I agree with examplens idea... I can imagine some DDOS attacks blackmailing dark net markets as they already are "XMR/BTC savvy" and generating a lot of money (perfect targets for this kind of activities IMO), but I'd be surprised if that was the case for a niche website like yours even if it is crypto-related.

I hope you get the hang of it soon bitmover!

There aren't many companies competing with cloudflare.like  aws and azure and a few more, but Cloudflare is the most used.

I use the free cloudlfare plan now.
Their cheapest plan is 200 usd per year.

How are you going to distinguish between me, who tries to access DDOSed site 5 times an hour to see if it's back up, and 5 million bots who each send one request per hour to the site?

This falls in the same category as anti-virus companies releasing computer viruses.

The server is hosted by Hetzner.
I have 50-100 sites (small and large) on the same server, only bitmover's site is under attack. 10+ years on the same contract, several upgrades in the meantime, all this gives me very little room that this bad intention came from there.

I also asked them for a solution to solve this problem and I got a very similar answer as I advised bitmover myself, somewhat more radical settings on cloudflare.
@joker_josue You have well suggested this for a DDoS protection service, I will talk to them about it and whether there are such possibilities.

As far as I can see, most of this bad traffic has been halted so far, CF seems to be doing its job.

But they already have this service: https://www.hetzner.com/unternehmen/ddos-schutz/
Now, it seems to me that it is only available in the WEBHOSTING or MANAGED SERVERS service.

If you are using the dedicated server, I think this service is not included. But, it may be possible for an additional cost. Or, since you are using a dedicated server, you can choose a service for yourself. In addition to Cloudflare, there is Imunify360 - https://www.imunify360.com - you can take a look.

I've been monitoring your total bandwidth for the last few days, it seems you have a bit more traffic compared to before the attack, but within tolerable limits. These days I also noticed that many sites are under similar pressures.

I don't have much experience with more advanced CloudFlare settings, but have you tried adding some exceptions, for FeeBuddy for example? I saw that in Security>>WAF there is an option to add custom rules to protect API and known bots from malicious traffic.
Missing FeeBuddy 

While it doesn't happen to me often, in some rare instances when I try to access the website I am presented with the following message:
Is this some sort of broken captcha page that perhaps isn't compatible with some settings that I have going on with my browser? After a few tries (or coming back later) the website just loads normally.