User ezscale , the webmaster of ezscale.cloud, joined AbuseIPDB in May 2023 and has reported 230,911 IP addresses.
Standing (weight) is good.
ACTIVE USER
WEBMASTER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇧🇷 201.17.208.212 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇵🇭 64.81.72.109 |
SSH brute force on gitea-runner (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 50.6.202.250 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇯🇵 111.238.174.6 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇫🇷 141.95.162.162 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 92.118.39.71 |
SSH brute force on gitea-runner (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 125.141.72.225 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 14.29.181.34 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 120.48.8.170 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 59.6.159.181 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇫🇷 185.157.247.92 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇼 197.243.14.52 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 42.96.17.249 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 125.142.37.91 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 50.6.205.78 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 156.232.13.246 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 115.191.38.87 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 121.15.140.235 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇺 37.110.142.162 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 119.23.248.16 |
SSH brute force on (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 64.89.163.90 |
SSH brute force on mysql-primary (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 180.184.71.166 |
SSH brute force on (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 2.57.121.112 |
SSH brute force on cp.vps.ezscale.tech (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 122.15.129.26 |
SSH brute force on (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 101.96.193.183 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH |