BNETv2 路 Network
Attacks observed on Infraly, LLC (AS400529)
BNETv2 attack observations affecting AS400529 Infraly, LLC: targeted prefixes, attack methods, destination ports, and timing over the last 30 days.
79 observations 路 Last 30 days 路 Latest observation
Most affected countries
Last 30 days
Most observed methods
Last 30 days
Recent observations
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.66/32UDP/301202mUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- TCP connection and payload flood185.244.106.7/32TCP/301203m 20sUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- UDP payload flood185.244.106.0/24UDP/301203m 20sUnited States
- UDP payload flood185.244.106.0/24UDP/UNKNOWN3m 20sUnited States
- UDP payload flood185.244.106.1/32UDP/301203m 20sUnited States
- UDP payload flood185.244.106.0/29UDP/301203m 20sUnited States
- UDP payload flood185.244.106.0/29UDP/UNKNOWN3m 20sUnited States
- UDP payload flood185.244.106.0/29UDP/UNKNOWN3m 20sUnited States
- UDP payload flood185.244.106.0/29UDP/UNKNOWN3m 20sUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
- TCP connection and payload flood185.244.106.7/32TCP/301202mUnited States
- UDP payload flood185.244.106.7/32UDP/301203m 20sUnited States
botnet.cl reports infrastructure it observed. An address appearing here identifies a target or a relay, not a person responsible for the attack.