Last active
December 7, 2025 05:08
-
-
Save kLiHz/5673b5c1d50794edb68c7d863dfc1242 to your computer and use it in GitHub Desktop.
An IP list for qBittorrent about (suspicious) peers (several CN IP CIDRs that causing hundreds of GBs upload traffic by downloading something again and agian),
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 101.70.158.0 - 101.70.158.255 | |
| 114.230.139.0 - 114.230.139.255 | |
| 115.238.230.0 - 115.238.231.255 | |
| 117.86.212.0 - 117.86.212.255 | |
| 121.231.30.0 - 121.231.30.255 | |
| 122.227.58.0 - 122.227.58.255 | |
| 124.91.148.0 - 124.91.148.255 | |
| 183.131.116.0 - 183.131.116.255 | |
| 183.131.177.0 - 183.131.177.255 | |
| 183.131.182.0 - 183.131.182.255 | |
| 183.131.216.0 - 183.131.216.255 | |
| 183.134.92.0 - 183.134.92.255 | |
| 183.136.216.0 - 183.136.216.255 | |
| 218.91.237.0 - 218.91.237.255 | |
| 218.93.63.0 - 218.93.63.255 | |
| 222.185.229.0 - 222.185.229.255 | |
| 36.27.216.0 - 36.27.216.255 | |
| 49.79.241.0 - 49.79.241.255 | |
| 58.216.100.0 - 58.216.100.255 | |
| 58.216.104.0 - 58.216.104.255 | |
| 58.216.23.0 - 58.216.23.255 | |
| 58.216.29.0 - 58.216.29.255 | |
| 58.216.33.0 - 58.216.33.255 | |
| 58.220.40.0 - 58.220.40.255 | |
| 60.162.168.0 - 60.162.171.255 | |
| 60.188.102.0 - 60.188.102.255 | |
| 60.188.108.0 - 60.188.108.255 | |
| 60.188.114.0 - 60.188.114.255 | |
| 60.188.92.0 - 60.188.92.255 | |
| 60.191.142.0 - 60.191.142.255 | |
| 61.147.88.0 - 61.147.88.255 | |
| 61.147.218.0 - 61.147.218.255 | |
| 61.147.223.0 - 61.147.223.255 | |
| 61.160.196.0 - 61.160.196.255 | |
| 61.160.198.0 - 61.160.198.255 | |
| 61.160.201.0 - 61.160.201.255 | |
| 61.160.235.0 - 61.160.235.255 | |
| 61.160.237.0 - 61.160.237.255 | |
| 61.160.241.0 - 61.160.242.255 | |
| 61.177.173.0 - 61.177.173.255 | |
| 240e:978:1508:0130:: - 240e:978:1508:0140:: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment