I usually seed about 100 or so transfers at once. Many of them have 100+ peers. I use an IP filter from Github and keep it updated. It's not unusual to have half of the peers filtered out for any given transfer, but many other problematic peers remain. I spend hours manually "ignoring" peers that the IP filter has missed.
It would be great if Tixati added the ability to easily filter peers based on IP address, range, country, or some combination thereof. For example, I have to manually filter all IPs beginning with 103.x.x.x that originate from Africa and several southeast Asian countries. There are literally thousands of them, and playing whack-a-mole for hours on end gets old really fast. Other examples are all IPs from Switzerland that begin with 213.55.x.x and most U.S. addresses beginning in 18.x.x.x, 35.x.x.x, 52.x.x.x, and 54.x.x.x.
Ironically, most of the addresses used by my VPN somehow ended up in the ipfilter.dat file. I have to log on and off several times before I can get an address that isn't filtered by other peers.
Does anyone else have this issue?

1. https://support.tixati.com/ip%20filter%20format  you can filter the subnets
2. When you add a new IP filter it tells you that you can filter countries like @US @PL
3. The blocklists found online are filled with trash to 99%. How did you not come to this conclusion when you started blocking your own VPN addresses? These are lists of abusive hosts, Bittorrent has no such concept as abusive hosts. Instead it has the problem of surveillance hosts that are unique to bittorrent and nobody does an automatic detection of them to my knowledge.
Many people must use VPNs and your list blocks VPNs. Counter productive!

If you want to efficiently block bittorrent botnets then start by blocking all AWS IPs. Then you can look up previous posts on these forums to see what blatant surveillance bots look like and block their IPs or /24 subnets.