User ezscale , the webmaster of ezscale.cloud, joined AbuseIPDB in May 2023 and has reported 197,160 IP addresses.
Standing (weight) is good.
ACTIVE USER
WEBMASTER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇳🇱 45.148.10.151 |
SSH brute force on cp.vps.ezscale.tech (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇯🇵 43.246.198.56 |
SSH brute force on atl-01.node.vps.ezscale.tech (4 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 172.252.13.101 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇸🇬 138.2.102.66 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇷 185.173.106.25 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇺 78.138.168.46 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 139.59.6.237 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 152.53.185.81 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 172.172.170.199 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 193.32.162.34 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇳🇱 91.92.42.34 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 172.172.186.3 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇦🇷 181.191.66.35 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇫🇷 141.95.162.162 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 193.32.162.34 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇸🇬 103.134.154.138 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇺 88.147.195.92 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 193.32.162.34 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇸🇪 158.174.211.17 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 211.51.132.104 |
SSH brute force on atl-02.node.vps.ezscale.tech (4 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 171.244.201.80 |
SSH brute force on atl-02.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 180.167.207.234 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 117.50.218.37 |
SSH brute force on support.ezscale.cloud (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 121.204.171.142 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇷🇴 80.94.92.234 |
SSH brute force on support (2 failures). Detected by fail2ban.
|
Brute-Force SSH |