User ezscale , the webmaster of ezscale.cloud, joined AbuseIPDB in May 2023 and has reported 230,515 IP addresses.
Standing (weight) is good.
ACTIVE USER
WEBMASTER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇨🇭 179.43.153.10 |
SSH brute force on (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 20.124.84.235 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇴 186.120.179.222 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 183.56.216.153 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 45.148.10.121 |
SSH brute force on support.ezscale.cloud (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇱🇰 220.247.224.226 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 182.76.115.214 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇵🇹 85.240.193.104 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 2.57.122.168 |
SSH brute force on cp.vps.ezscale.tech (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇯🇵 111.238.174.6 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 2.57.121.25 |
SSH brute force on cp.vps.ezscale.tech (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 180.76.146.235 |
SSH brute force on gitea-runner (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 123.187.244.19 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇭 209.99.190.186 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇯🇵 118.194.228.101 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇺 109.63.176.105 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 61.155.106.101 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 36.104.147.6 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 14.103.107.234 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇲🇽 189.204.230.91 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇩 36.64.131.68 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 64.89.163.164 |
SSH brute force on mysql-primary (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 36.140.151.122 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 64.89.163.142 |
SSH brute force on mysql-primary (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 109.160.32.152 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH |