Welcome to the new IP check page! We're rolling it out gradually and would love your input. Spot a bug, or have a suggestion?
Share feedback
172.68.134.14
Neutral Activity
There is no recent abuse activity, or the IP address is whitelisted.
Whitelisted Subnet
Whitelisted netblocks are typically owned by trusted entities, such as Google or Microsoft who
may use them for search engine spiders. However, these same entities sometimes also provide cloud
servers and mail services which are easily abused. Pay special attention when trusting or
distrusting these IPs.
Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 172.68.134.14:
This IP address has been reported a total of
30
times from
8 distinct
sources.
172.68.134.14 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Brazil
with 4
reports;
United Kingdom of Great Britain and Northern Ireland
with 1
report.
The most common categories in these recent reports were:
SSH
5
times;
Brute-Force
5
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
2026-09-04T19:11:03.643960+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[2833843]: Invalid user t ...
show more2026-09-04T19:11:03.643960+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[2833843]: Invalid user tactical from 172.68.134.14 port 64920
2026-09-04T19:11:03.793606+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[2833843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.68.134.14
2026-09-04T19:11:05.445914+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[2833843]: Failed password for invalid user tactical from 172.68.134.14 port 64920 ssh2
...
show less
2026-08-30T17:26:40.381759+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1958757]: Failed passwor ...
show more2026-08-30T17:26:40.381759+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1958757]: Failed password for root from 172.68.134.14 port 57806 ssh2
2026-08-30T17:26:43.765630+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1958757]: Failed password for root from 172.68.134.14 port 57806 ssh2
2026-08-30T17:26:48.092800+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1958757]: Failed password for root from 172.68.134.14 port 57806 ssh2
...
show less
2026-08-29T01:03:43.490955+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1677297]: pam_unix(sshd: ...
show more2026-08-29T01:03:43.490955+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1677297]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.68.134.14
2026-08-29T01:03:45.432518+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1677297]: Failed password for invalid user piyush from 172.68.134.14 port 61316 ssh2
2026-08-29T01:08:51.444999+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1678009]: Invalid user debian from 172.68.134.14 port 49508
...
show less
2026-08-28T07:43:40.597709+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1550471]: Failed passwor ...
show more2026-08-28T07:43:40.597709+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1550471]: Failed password for invalid user root1 from 172.68.134.14 port 59555 ssh2
2026-08-28T07:45:25.161189+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1550730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.68.134.14 user=root
2026-08-28T07:45:27.029030+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[1550730]: Failed password for root from 172.68.134.14 port 51274 ssh2
...
show less
2026-08-25T04:15:12.064588+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[995836]: pam_unix(sshd:a ...
show more2026-08-25T04:15:12.064588+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[995836]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.68.134.14
2026-08-25T04:15:13.977882+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[995836]: Failed password for invalid user jael from 172.68.134.14 port 52303 ssh2
2026-08-25T04:15:16.713316+00:00 edge-con-sao01.int.pdx.net.uk sshd-session[995836]: Failed password for invalid user jael from 172.68.134.14 port 52303 ssh2
...
show less
Blocked by UFW (TCP on port 443).
Source port: 59752
TTL: 47
Packet length: 40
TOS: 0x00
Timestamp: ...
show moreBlocked by UFW (TCP on port 443).
Source port: 59752
TTL: 47
Packet length: 40
TOS: 0x00
Timestamp: 2024-09-08 14:23:50 [Europe/Warsaw]
This report (for 172.68.134.14) was generated by:
https://github.com/sefinek24/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW (TCP on port 443).
Source port: 54408
TTL: 47
Packet length: 40
TOS: 0x00
Timestamp: ...
show moreBlocked by UFW (TCP on port 443).
Source port: 54408
TTL: 47
Packet length: 40
TOS: 0x00
Timestamp: 2024-09-04 14:12:37 [Europe/Warsaw]
This report (for 172.68.134.14) was generated by:
https://github.com/sefinek24/UFW-AbuseIPDB-Reporter
show less
IP: 172.68.134.14
Protocol: TCP
Source port: 9400
Destination port: 443
TTL: 47
Packet length: 40
TO ...
show moreIP: 172.68.134.14
Protocol: TCP
Source port: 9400
Destination port: 443
TTL: 47
Packet length: 40
TOS: 0x00
Timestamp: Aug 18 03:57:58 (03:57:58, 18.08.2024)
The IP address was blocked by the Uncomplicated Firewall (UFW) due to suspicious activity. Packet details suggest a possible unauthorized access or port scanning attempt.
show less
