User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇦🇺 45.134.20.152 |
DDoS composite score 31.0 (proxy tier) - 514 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 51.104.44.27 |
DDoS composite score 20.3 (challenge tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 81.171.72.135 |
DDoS composite score 16.3 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.178 |
DDoS composite score 23.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.184 |
DDoS composite score 23.2 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:322f:6590:5944:a3f:b566:a428 |
DDoS composite score 25.5 (challenge tier) - 78 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 2a0b:8bc0:2:807c::1 |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 23.27.145.238 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇭 43.164.1.211 |
DDoS composite score 29.1 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.164.192.151 |
DDoS composite score 34.0 (proxy tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.164.196.244 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.164.197.117 |
DDoS composite score 24.2 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.167.245.18 |
DDoS composite score 22.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.154.98.101 |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 72.167.132.114 |
DDoS composite score 19.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 93.152.221.118 |
DDoS composite score 20.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 104.207.62.57 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 162.216.148.0 |
DDoS composite score 16.3 (challenge tier) - 108 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 165.232.178.144 |
DDoS composite score 19.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.35.153 |
DDoS composite score 26.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.225.200.207 |
DDoS composite score 22.5 (challenge tier) - 195 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇺 2a09:bac5:51ad:369::57:21a |
DDoS composite score 35.9 (proxy tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 58.187.66.226 |
DDoS composite score 25.5 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.229 |
DDoS composite score 23.2 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 20.195.178.90 |
DDoS composite score 21.2 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack |