User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 67.165.79.118 |
DDoS composite score 43.8 (challenge tier) - 82 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.94.22.247 |
DDoS composite score 41.2 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 51.107.222.225 |
DDoS composite score 53.3 (challenge tier) - 145 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 2001:41d0:701:1100::2444 |
DDoS composite score 44.8 (challenge tier) - 184 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.200.222.0 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 51.13.190.245 |
DDoS composite score 34.6 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇹 172.213.152.251 |
DDoS composite score 38.6 (challenge tier) - 46 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇶 212.237.123.134 |
DDoS composite score 36.9 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 40.85.253.121 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 93.123.109.214 |
DDoS composite score 37.3 (challenge tier) - 69 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 172.94.9.253 |
DDoS composite score 42.5 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 20.100.169.43 |
DDoS composite score 60.1 (proxy tier) - 70 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 20.215.216.144 |
DDoS composite score 37.9 (challenge tier) - 43 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 20.166.7.149 |
DDoS composite score 34.6 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 51.103.25.236 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 185.177.72.29 |
DDoS composite score 37.3 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 250 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.83.46.198 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 104.46.233.222 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.15.7 |
DDoS composite score 32.4 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 104.197.69.115 |
DDoS composite score 37.9 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 194.165.16.5 |
DDoS composite score 33.7 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 2001:41d0:801:2000::4d84 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇹 84.37.154.37 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇺🇸 173.208.162.87 |
DDoS composite score 65.0 (proxy tier) - 156 reqs/5min - high_traffic
|
DDoS Attack |