User ezscale , the webmaster of ezscale.cloud, joined AbuseIPDB in May 2023 and has reported 204,983 IP addresses.
Standing (weight) is good.
ACTIVE USER
WEBMASTER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇰🇷 39.120.34.60 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 223.243.179.70 |
SSH brute force on gitea-runner (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 | |
| 🇩🇪 217.160.64.31 |
SSH brute force on atl-03.node.vps.ezscale.tech (2 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇭🇰 219.78.63.235 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇧🇬 109.160.32.98 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 106.243.155.71 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇲🇽 189.204.230.91 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 125.20.16.22 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇻🇳 45.117.177.47 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 122.168.123.73 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 172.203.149.63 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇩 163.7.11.126 |
SSH brute force on node01.fsn1.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇿 185.233.3.95 |
SSH brute force on support (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇰🇷 106.243.155.71 |
SSH brute force on atl-01.node.vps.ezscale.tech (5 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 180.76.137.24 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 99.92.204.98 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇴 190.60.43.28 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇫🇷 54.38.180.48 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇫🇷 91.134.133.184 |
SSH brute force on atl-03.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇿 213.230.111.14 |
SSH brute force on scp.dedicated.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇺🇸 192.210.206.252 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇨🇳 61.182.67.242 |
SSH brute force on cp.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇮🇳 182.70.255.242 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH | |
| 🇩🇪 207.154.230.149 |
SSH brute force on atl-01.node.vps.ezscale.tech (3 failures). Detected by fail2ban.
|
Brute-Force SSH |