Potassium 路 Country
Attacks observed in Luxembourg
Potassium attack observations affecting networks in Luxembourg: targeted prefixes, affected operators, attack methods, and timing over the last 30 days.
46 observations 路 Last 30 days 路 Latest observation
Most affected networks
Last 30 days
Most observed methods
Last 30 days
Recent observations
- UDP datagram flood, variant 7202.78.161.128/32UDP/801mLuxembourg
- UDP datagram flood, variant 7202.78.161.128/32UDP/532mLuxembourg
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxembourg
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxembourg
- UDP datagram flood, variant 7193.239.179.18/32UDP/255652mLuxembourg
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxembourg
- Mixed TCP/UDP flood202.78.161.128/32TCP/UDP/2230sLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/210658sLuxembourg
- TCP connection flood193.239.179.145/32TCP/210658sLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- UDP datagram flood, variant 7202.78.161.128/32UDP/5330sLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21062mLuxembourg
- TCP connection flood193.239.179.145/32TCP/21061mLuxembourg
botnet.cl reports infrastructure it observed. An address appearing here identifies a target or a relay, not a person responsible for the attack.