User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 104.197.69.115 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 206.204.14.158 |
DDoS composite score 43.8 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.23.218.208 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 207.46.13.111 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.225.247.125 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.30 |
DDoS composite score 47.7 (challenge tier) - 317 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 38.248.95.254 |
DDoS composite score 42.8 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.182.159.36 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2401:d800:9c7:309e:9057:612a:4dbf:7006 |
DDoS composite score 31.7 (challenge tier) - 165 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:4304:52c0:81c:a47a:f839:ad83 |
DDoS composite score 36.9 (challenge tier) - 139 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.182.161.116 |
DDoS composite score 55.2 (challenge tier) - 278 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.4.250.211 |
DDoS composite score 37.9 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 13.158.77.167 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.93.83.156 |
DDoS composite score 37.9 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 168.144.46.105 |
DDoS composite score 34.6 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.89.6 |
DDoS composite score 43.8 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 52.243.57.116 |
DDoS composite score 42.8 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 40.115.139.4 |
DDoS composite score 37.3 (challenge tier) - 75 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.228.84.35 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 207.46.13.17 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a09:bac5:a6c2:197d::28a:32 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 95.181.239.18 |
DDoS composite score 36.3 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.167.144.176 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.60 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.167 |
DDoS composite score 60.1 (proxy tier) - 104 reqs/5min - high_traffic
|
DDoS Attack |