This IP address has been reported a total of
10
times from
9 distinct
sources.
137.184.206.136 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
France
with 1
report;
India
with 1
report;
Netherlands
with 1
report.
The most common categories in these recent reports were:
Port Scan
4
times;
SSH
1
time;
Brute-Force
1
time.
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-10-15T14:22:41.592770+02:00 ubuntu-server sshd[1632379]: banner exchange: Connection from 137.1 ...
show more2026-10-15T14:22:41.592770+02:00 ubuntu-server sshd[1632379]: banner exchange: Connection from 137.184.206.136 port 39362: invalid format
...
show less
Honeypot Finding: repeated TCP service probing on TCP/55555 (service); 2 application-level events ac ...
show moreHoneypot Finding: repeated TCP service probing on TCP/55555 (service); 2 application-level events across 2 source port(s). Sensor(s): Honeytrap.
show less
Blocked by UFW (TCP on 8001)
Source port: 61008
TTL: 242
Packet length: 44
TOS: 0x00
This report (f ...
show moreBlocked by UFW (TCP on 8001)
Source port: 61008
TTL: 242
Packet length: 44
TOS: 0x00
This report (for 137.184.206.136) was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW on Jellyfin [8880/tcp]
Source port: 61002
TTL: 239
Packet length: 44
TOS: 0x08
This ...
show moreBlocked by UFW on Jellyfin [8880/tcp]
Source port: 61002
TTL: 239
Packet length: 44
TOS: 0x08
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Auto-ban: 12 malicious requests on 2026-04-09 (e.g., env/backup probes, brute-force, or error bursts ...
show moreAuto-ban: 12 malicious requests on 2026-04-09 (e.g., env/backup probes, brute-force, or error bursts).
show less
