143.202.139.122
| ISP | Infosport SA |
|---|---|
| Usage Type | Fixed Line ISP |
| ASN | AS263196 |
| Hostname(s) | customer-139-122.telwinet.com.ar |
| Domain Name | optimix.com.ar |
| Country | 🇦🇷 Argentina |
| City | Pontevedra, Buenos Aires |
ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
IP Abuse Reports for 143.202.139.122
This IP address has been reported a total of 26 times from 19 distinct sources. 143.202.139.122 was first reported on , and the most recent report was . In the last 60 days, the top reporter locations were: Germany with 6 reports; France with 2 reports; United States of America with 2 reports. The most common categories in these recent reports were: Port Scan 7 times; Brute-Force 3 times; SSH 3 times; DDoS Attack 3 times; Email Spam 2 times; Other 6 times.
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇦🇷 Bruno |
Port Scanner: 143.202.139.122
|
Port Scan | ||
| 🇬🇧 Stuart Reid |
...
|
SSH | ||
| 🇩🇪 Jochen Pretli |
connection to honeypot
|
Email Spam Port Scan | ||
| Anonymous |
denied traffic to a honeypot network. destination port 22.
|
Port Scan Hacking | ||
| 🇩🇪 Jochen Pretli |
connection to honeypot
|
Email Spam Port Scan | ||
| Anonymous |
denied SSH access attempt. destination port 22.
|
Port Scan Brute-Force SSH | ||
| 🇺🇸 NetVexor |
Attack source identified and submitted via NetVexor BGP Blackhole Network
|
Port Scan Hacking Brute-Force | ||
| Anonymous |
denied SSH access attempt. destination port 22.
|
Port Scan Brute-Force SSH | ||
| 🇫🇷 Zkillu |
|
DDoS Attack Exploited Host | ||
| 🇫🇷 dmallet |
|
DDoS Attack Exploited Host | ||
| 🇩🇪 pltcldvlpr |
|
Bad Web Bot | ||
| 🇺🇸 kosada.com |
Web bot: denial-of-service flood
|
DDoS Attack Bad Web Bot | ||
| Anonymous |
Unauthorized connection attempt on Port 23
|
Port Scan Hacking Exploited Host | ||
| 🇺🇸 cybsecaoccol |
unauthorized connection or malicious port scan attempted on tcp port - corp
|
Port Scan Hacking | ||
| 🇨🇦 polycoda |
🥶 Part of massive botnet scraping campaign that nearly turned into a DDoS on 2025-11-27
|
DDoS Attack |
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩