User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 136.118.99.12 |
DDoS composite score 43.8 (challenge tier) - 110 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.49.151 |
DDoS composite score 37.9 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.131.45.213 |
DDoS composite score 37.9 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.167.157.80 |
DDoS composite score 39.5 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.157.95.239 |
DDoS composite score 37.9 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 49.51.183.75 |
DDoS composite score 37.9 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 3.82.143.83 |
DDoS composite score 43.8 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.154.56 |
DDoS composite score 37.9 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:613d:4f74:7c69:f7c5:8bca:f44d |
DDoS composite score 36.9 (challenge tier) - 126 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.48.184.58 |
DDoS composite score 60.1 (proxy tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.151.96 |
DDoS composite score 43.8 (challenge tier) - 58 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 157.66.55.50 |
DDoS composite score 56.9 (challenge tier) - 71 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.154.143.25 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 2001:1970:4ade:800:e671:3bab:b41f:1140 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇸 141.98.103.251 |
DDoS composite score 37.9 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 151 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 193.32.249.134 |
DDoS composite score 31.4 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.15.7 |
DDoS composite score 37.3 (challenge tier) - 58 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.120 |
DDoS composite score 38.9 (challenge tier) - 131 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 2a01:4f8:c17:6327::1 |
DDoS composite score 38.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.198.86.98 |
DDoS composite score 60.1 (proxy tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.77.77 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 173.208.162.87 |
DDoS composite score 61.1 (proxy tier) - 121 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇺🇸 172.190.142.176 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack |