User ezscale , the webmaster of ezscale.cloud, joined AbuseIPDB in May 2023 and has reported 215,190 IP addresses.
Standing (weight) is good.
ACTIVE USER
WEBMASTER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇮🇳 103.123.53.88 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇲🇾 202.165.15.132 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇦🇺 34.40.145.110 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇧🇴 190.129.122.185 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 64.89.163.180 |
SSH brute force on mysql-primary (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 112.219.151.50 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 180.76.138.16 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 40.138.166.230 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇪🇨 186.68.83.104 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 167.71.72.95 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 103.216.170.15 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇹 151.59.131.203 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 103.200.22.154 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇹🇼 152.32.230.104 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇸🇬 43.159.62.8 |
SSH brute force on gitea-runner (4 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 103.98.161.85 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 195.242.119.58 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 213.206.207.162 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 172.208.48.177 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇵 202.63.242.138 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 103.146.23.23 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇸🇬 101.47.14.46 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 101.96.205.145 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 64.89.163.165 |
SSH brute force on mysql-primary (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇯🇵 118.194.228.101 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH |