User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 224 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.219.138.200 |
DDoS composite score 34.6 (challenge tier) - 48 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 211.235.74.125 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 107.172.195.52 |
DDoS composite score 41.2 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.151.71 |
DDoS composite score 43.8 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 20.240.58.31 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 157.66.55.50 |
DDoS composite score 40.5 (challenge tier) - 90 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 132.196.61.110 |
DDoS composite score 34.6 (challenge tier) - 50 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.68 |
DDoS composite score 57.5 (challenge tier) - 58 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.47.52.244 |
DDoS composite score 43.8 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.198.83.136 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.15.7 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 40.85.253.121 |
DDoS composite score 48.0 (challenge tier) - 182 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 93.123.109.214 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2600:1900:0:4006::301 |
DDoS composite score 43.8 (challenge tier) - 89 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.167.144.180 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 98.116.58.8 |
DDoS composite score 43.8 (challenge tier) - 81 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 173.208.162.87 |
DDoS composite score 65.0 (proxy tier) - 289 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.70.169 |
DDoS composite score 43.8 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 4.225.164.196 |
DDoS composite score 34.6 (challenge tier) - 43 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 68.183.37.191 |
DDoS composite score 34.6 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.48.184.58 |
DDoS composite score 47.1 (challenge tier) - 392 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 51.103.25.236 |
DDoS composite score 37.3 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 185.177.72.29 |
DDoS composite score 64.1 (proxy tier) - 503 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 2408:8266:5001:d3fd:2ec4:4fff:fea0:c1ad |
DDoS composite score 43.8 (challenge tier) - 69 reqs/5min - high_traffic
|
DDoS Attack |