User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 64.233.172.68 |
DDoS composite score 57.5 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.77.167.7 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 52.16.3.16 |
DDoS composite score 43.8 (challenge tier) - 60 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 52.187.249.150 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 149.102.234.44 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 107.172.195.93 |
DDoS composite score 32.4 (challenge tier) - 65 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 57.129.4.123 |
DDoS composite score 43.8 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 113.31.186.146 |
DDoS composite score 37.9 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 134.209.42.24 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.77.76 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 183.134.59.133 |
DDoS composite score 37.9 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 195.178.110.33 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 52.243.57.116 |
DDoS composite score 37.3 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 126.254.158.70 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.219.218.121 |
DDoS composite score 37.3 (challenge tier) - 67 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.123.170.104 |
DDoS composite score 43.8 (challenge tier) - 70 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 128.242.238.48 |
DDoS composite score 34.6 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 100.54.104.182 |
DDoS composite score 36.9 (challenge tier) - 119 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 2a0b:8bc0:2:6a17::1 |
DDoS composite score 34.6 (challenge tier) - 46 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.74 |
DDoS composite score 57.5 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 84.39.227.255 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 51.38.135.19 |
DDoS composite score 43.8 (challenge tier) - 120 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 44.222.113.209 |
DDoS composite score 57.5 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 167.114.3.106 |
DDoS composite score 43.8 (challenge tier) - 138 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 2001:41d0:801:2000::4d84 |
DDoS composite score 43.8 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack |