Potassium 路 Network
Attacks observed on DODOLINK INTERNACIONAL SRL (AS64123)
Potassium attack observations affecting AS64123 DODOLINK INTERNACIONAL SRL: targeted prefixes, attack methods, destination ports, and timing over the last 30 days.
74 observations 路 Last 30 days 路 Latest observation
Most affected countries
Last 30 days
Most observed methods
- UDP datagram flood, variant 759
- TCP connection flood12
- UDP datagram flood, variant 132
- Mixed TCP/UDP flood1
Last 30 days
Recent observations
- UDP datagram flood, variant 7186.148.225.226/32UDP/83011mArgentina
- UDP datagram flood, variant 7128.254.190.154/32UDP/531m 40sArgentina
- UDP datagram flood, variant 7186.148.224.107/32UDP/531m 40sArgentina
- UDP datagram flood, variant 7186.148.224.2/32UDP/44431m 40sArgentina
- UDP datagram flood, variant 738.210.207.2/32UDP/500001m 40sArgentina
- TCP connection flood128.254.190.134/32TCP/80801m 40sArgentina
- UDP datagram flood, variant 7186.148.224.166/32UDP/90901mArgentina
- TCP connection flood128.254.191.213/32TCP/1101m 40sArgentina
- UDP datagram flood, variant 7128.254.191.18/32UDP/691m 40sArgentina
- TCP connection flood206.0.31.209/32TCP/23771m 40sArgentina
- UDP datagram flood, variant 7128.254.189.56/32UDP/23051m 40sArgentina
- UDP datagram flood, variant 738.210.207.163/32UDP/534131m 40sArgentina
- UDP datagram flood, variant 7186.148.225.111/32UDP/42221m 40sArgentina
- UDP datagram flood, variant 7206.0.31.95/32UDP/80001mArgentina
- UDP datagram flood, variant 7128.254.189.238/32UDP/14331m 40sArgentina
- UDP datagram flood, variant 7155.103.131.114/32UDP/1231m 40sArgentina
- UDP datagram flood, variant 7186.148.227.94/32UDP/616131m 40sArgentina
- UDP datagram flood, variant 7128.254.189.189/32UDP/54731m 40sArgentina
- UDP datagram flood, variant 738.210.207.114/32UDP/23041m 40sArgentina
- UDP datagram flood, variant 7128.254.191.120/32UDP/221m 40sArgentina
- UDP datagram flood, variant 7128.254.191.127/32UDP/83001m 40sArgentina
- UDP datagram flood, variant 7128.254.188.56/32UDP/811m 40sArgentina
- TCP connection flood186.148.227.28/32TCP/4431m 40sArgentina
- UDP datagram flood, variant 7128.254.191.133/32UDP/531m 40sArgentina
- UDP datagram flood, variant 7186.148.225.9/32UDP/37841m 40sArgentina
- UDP datagram flood, variant 7155.103.131.58/32UDP/54061m 40sArgentina
- UDP datagram flood, variant 7186.148.227.114/32UDP/84721m 40sArgentina
- UDP datagram flood, variant 13128.254.191.168/32UDP/33061mArgentina
- UDP datagram flood, variant 7128.254.190.218/32UDP/280151m 40sArgentina
- UDP datagram flood, variant 7186.148.226.36/32UDP/91001mArgentina
- UDP datagram flood, variant 7186.148.225.70/32UDP/531m 40sArgentina
- UDP datagram flood, variant 7186.148.227.230/32UDP/94111m 40sArgentina
- UDP datagram flood, variant 7186.148.227.230/32UDP/94111mArgentina
- TCP connection flood128.254.191.159/32TCP/100221m 40sArgentina
- UDP datagram flood, variant 7186.148.226.173/32UDP/84481m 40sArgentina
- UDP datagram flood, variant 7128.254.190.33/32UDP/90011m 40sArgentina
- UDP datagram flood, variant 7128.254.191.165/32UDP/531m 40sArgentina
- UDP datagram flood, variant 7186.148.225.123/32UDP/801m 40sArgentina
- TCP connection flood128.254.191.59/32TCP/88801mArgentina
- TCP connection flood128.254.191.59/32TCP/88801m 40sArgentina
botnet.cl reports infrastructure it observed. An address appearing here identifies a target or a relay, not a person responsible for the attack.