User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 51.81.245.138 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a03:2880:16ff:4a:: |
DDoS composite score 43.8 (challenge tier) - 65 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 183.249.66.40 |
DDoS composite score 36.9 (challenge tier) - 107 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.59 |
DDoS composite score 43.8 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 139.0.7.2 |
DDoS composite score 34.6 (challenge tier) - 5 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.89.94.189 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 119.12.189.223 |
DDoS composite score 37.9 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 88.99.48.186 |
DDoS composite score 43.8 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 2a01:4f8:1c19:54a0::1 |
DDoS composite score 32.4 (challenge tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 149.102.234.29 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.16.28.40 |
DDoS composite score 63.4 (proxy tier) - 147 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 85.10.204.138 |
DDoS composite score 49.3 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 52.243.57.116 |
DDoS composite score 64.1 (proxy tier) - 159 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 134.122.28.88 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 150.136.145.228 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 172.252.115.118 |
DDoS composite score 36.9 (challenge tier) - 113 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 143.110.213.72 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.226.16.193 |
DDoS composite score 36.9 (challenge tier) - 111 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 222.252.42.56 |
DDoS composite score 36.9 (challenge tier) - 119 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 159.54.168.85 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.225.184.174 |
DDoS composite score 36.9 (challenge tier) - 144 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 207 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 95.181.239.15 |
DDoS composite score 56.9 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 2a05:d018:1d9d:e700:7a00:6a30:186a:4c77 |
DDoS composite score 32.7 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.167 |
DDoS composite score 60.1 (proxy tier) - 130 reqs/5min - high_traffic
|
DDoS Attack |