User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇯🇵 20.78.172.67 |
DDoS composite score 60.1 (proxy tier) - 59 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 18.234.66.51 |
DDoS composite score 43.8 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.151.71 |
DDoS composite score 41.2 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.4.251.220 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 259 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a09:bac5:a6c3:197d::28a:51 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇹 193.47.56.148 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:4a54:5f10:ca66:756c:4200:9294 |
DDoS composite score 31.7 (challenge tier) - 229 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.153 |
DDoS composite score 43.8 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.122.147.229 |
DDoS composite score 37.9 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 178.171.115.216 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.200.222.0 |
DDoS composite score 37.3 (challenge tier) - 85 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 52.243.57.116 |
DDoS composite score 37.3 (challenge tier) - 88 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 159.65.225.121 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2600:1900:4020:5ea:0:368:: |
DDoS composite score 43.8 (challenge tier) - 97 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 2a0b:8bc0:2:6a17::1 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 52.187.249.150 |
DDoS composite score 37.3 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 167.71.175.236 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 206.81.24.74 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 24.199.81.247 |
DDoS composite score 37.9 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 159.65.144.72 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 141.98.11.17 |
DDoS composite score 70.9 (proxy tier) - 165 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.229.236.73 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 209.170.91.200 |
DDoS composite score 43.8 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 100.55.86.182 |
DDoS composite score 57.5 (challenge tier) - 83 reqs/5min - high_traffic
|
DDoS Attack |