Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
134.199.166.199 has been reported 89
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
2026-03-14T11:17:17.139561+01:00 Proxmox sshd-session[3923859]: Invalid user admin from 134.199.166.199 port 33302
2026-03-14T11:18:17.513662+01:00 Proxmox sshd-session[3924632]: Invalid user admin from 134.199.166.199 port 54072
2026-03-14T11:19:22. ...
show more2026-03-14T11:17:17.139561+01:00 Proxmox sshd-session[3923859]: Invalid user admin from 134.199.166.199 port 33302
2026-03-14T11:18:17.513662+01:00 Proxmox sshd-session[3924632]: Invalid user admin from 134.199.166.199 port 54072
2026-03-14T11:19:22.147550+01:00 Proxmox sshd-session[3925519]: Invalid user admin from 134.199.166.199 port 57702
...
show less
2026-03-14T10:17:00.791344+00:00 database-prodv1-game sshd[645454]: Invalid user admin from 134.199.166.199 port 55806
2026-03-14T10:18:00.778327+00:00 database-prodv1-game sshd[649308]: Invalid user admin from 134.199.166.199 port 35730
2026-03-14T1 ...
show more2026-03-14T10:17:00.791344+00:00 database-prodv1-game sshd[645454]: Invalid user admin from 134.199.166.199 port 55806
2026-03-14T10:18:00.778327+00:00 database-prodv1-game sshd[649308]: Invalid user admin from 134.199.166.199 port 35730
2026-03-14T10:19:04.620771+00:00 database-prodv1-game sshd[653864]: Invalid user admin from 134.199.166.199 port 40264
...
show less
Mar 14 11:03:51 bsd01 sshd-session[49798]: Connection closed by 134.199.166.199 port 53166
Mar 14 11:06:37 bsd01 sshd-session[49987]: Connection closed by authenticating user root 134.199.166.199 port 46518 [preauth]
Mar 14 11:07:51 bsd01 sshd-sessio ...
show moreMar 14 11:03:51 bsd01 sshd-session[49798]: Connection closed by 134.199.166.199 port 53166
Mar 14 11:06:37 bsd01 sshd-session[49987]: Connection closed by authenticating user root 134.199.166.199 port 46518 [preauth]
Mar 14 11:07:51 bsd01 sshd-session[50016]: Connection closed by authenticating user root 134.199.166.199 port 60848 [preauth]
Mar 14 11:09:05 bsd01 sshd-session[50182]: Connection closed by authenticating user root 134.199.166.199 port 56490 [preauth]
Mar 14 11:10:26 bsd01 sshd-session[50230]: Connection closed by authenticating user root 134.199.166.199 port 54024 [preauth]
...
show less
2026-03-14T10:07:21.371729+00:00 sg-jumphost-server sshd[2460832]: Connection closed by authenticating user root 134.199.166.199 port 48630 [preauth]
2026-03-14T10:08:36.425846+00:00 sg-jumphost-server sshd[2460865]: Connection closed by authenticati ...
show more2026-03-14T10:07:21.371729+00:00 sg-jumphost-server sshd[2460832]: Connection closed by authenticating user root 134.199.166.199 port 48630 [preauth]
2026-03-14T10:08:36.425846+00:00 sg-jumphost-server sshd[2460865]: Connection closed by authenticating user root 134.199.166.199 port 46942 [preauth]
2026-03-14T10:09:49.641246+00:00 sg-jumphost-server sshd[2460886]: Connection closed by authenticating user root 134.199.166.199 port 32830 [preauth]
...
show less
Mar 14 05:08:03 wp sshd[2896731]: Failed password for root from 134.199.166.199 port 50700 ssh2
Mar 14 05:09:14 wp sshd[2897262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.166.199 user=root
Mar 1 ...
show moreMar 14 05:08:03 wp sshd[2896731]: Failed password for root from 134.199.166.199 port 50700 ssh2
Mar 14 05:09:14 wp sshd[2897262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.199.166.199 user=root
Mar 14 05:09:16 wp sshd[2897262]: Failed password for root from 134.199.166.199 port 45884 ssh2
...
show less