IP abuse report193.176.31.198

Suspicious Hosting / Datacenter IPv4 The Netherlands AS25369

193.176.31.198 is an IPv4 address located in Amsterdam, The Netherlands. It belongs to a network operated by Hydra Communications Ltd (AS25369). The address is listed by 1 of the threat-intelligence sources we track and carries a confidence score of 40/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 1 Community Reports 1 How the score works
Provider notified This IP was reported to its network operator Hydra Communications Ltd · 2026-09-22 · IPDB-AR-000032 Awaiting reply Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-09-22 23:49
  3. Deliveredinfrawat.ch
  4. Operator response Waiting · 1 month ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Hydra Communications Ltd's registered abuse contact on 2026-09-22 23:49: abuse@infrawat.ch

This notice covers 100 address(es) on the same network. View public record · IPDB-AR-000032 →
Listing sources1
Community Reports1
Distinct Reporters1
Last seen 6 days ago

IP Information

ISP / Organization
Hydra Communications Ltd
ASN
AS25369 BANDWIDTH-AS
ASN Domain
zare.com
IP Range
193.176.31.192/26
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
The Netherlands (NL)
Region / State
North Holland
City
Amsterdam 2 sources agree
Time Zone
Europe/Amsterdam
Abuse contact
abuse@infrawat.ch The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Amsterdam North Holland, The Netherlands
Coordinates
52.37, 4.90
Network
AS25369 Hydra Communications Ltd
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

193.176.31.0/24

61 of the 256 addresses in 193.176.31.0/24 are listed by our sources (23.8%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
193.176.31.149193.176.31.150193.176.31.151193.176.31.152193.176.31.153193.176.31.155193.176.31.156193.176.31.157

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

1
Aggregated List (Low Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 3 Aggregator 193.176.31.0/24 2026-11-18 14:47 2026-11-20 06:481 minute ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 193.176.31.198 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 193.176.31.198 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 193.176.31.198 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 193.176.31.198 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. nak Registered member
    6 days ago 2026-11-14 02:50Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 1 requests on 2026-11-13 12:15:54–12:15:54 UTC (0 s). Automated MCP endpoint scanner. Attack attempts: - MCP endpoint probing: GET /mcp/ -> discovers Model Context Protocol server capabilities Signatures: ai-triage

Reporters' IP addresses are never published — only the country they reported from.

Listing History

32
Removed from the pool
2 hours ago · score at the time: 90/100 · carried by 2 sources
2026-11-20 04:22
Added to the pool
4 hours ago
2026-11-20 02:22
Removed from the pool
yesterday · score at the time: 65/100 · carried by 1 sources
2026-11-19 05:22
Added to the pool
16 days ago
2026-11-03 16:22
Removed from the pool
16 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-03 12:22
Added to the pool
17 days ago
2026-11-03 01:22
Removed from the pool
17 days ago · score at the time: 90/100 · carried by 2 sources
2026-11-03 00:22
Added to the pool
18 days ago
2026-11-02 03:22
Removed from the pool
18 days ago · score at the time: 90/100 · carried by 2 sources
2026-11-02 02:22
Added to the pool
20 days ago
2026-10-31 01:22
Removed from the pool
20 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-31 00:22
Added to the pool
23 days ago
2026-10-27 23:22
Removed from the pool
23 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-27 22:22
Added to the pool
23 days ago
2026-10-27 14:22
Removed from the pool
23 days ago · score at the time: 50/100 · carried by 1 sources
2026-10-27 12:22
Added to the pool
24 days ago
2026-10-27 01:22
Removed from the pool
24 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-27 00:22
Added to the pool
26 days ago
2026-10-24 23:22
Removed from the pool
26 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-24 21:22
Added to the pool
26 days ago
2026-10-24 18:22
Removed from the pool
26 days ago · score at the time: 60/100 · carried by 1 sources
2026-10-24 17:22
Added to the pool
26 days ago
2026-10-24 16:22
Removed from the pool
26 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-24 13:22
Added to the pool
27 days ago
2026-10-24 04:22
Removed from the pool
27 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-24 03:22
Added to the pool
27 days ago
2026-10-23 20:22
Removed from the pool
27 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-23 19:22
Added to the pool
27 days ago
2026-10-23 15:22
Removed from the pool
27 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-23 13:22
Added to the pool
28 days ago
2026-10-23 02:22
Removed from the pool
28 days ago · score at the time: 90/100 · carried by 3 sources
2026-10-23 01:22
Added to the pool
2 months ago · score at the time: 90/100 · carried by 4 sources
2026-08-28 11:17

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 193.176.31.198

Is 193.176.31.198 safe?

193.176.31.198 scores 40/100 from several independent signals (1 source, 1 community report). Rate-limit or challenge its traffic and review your logs for it.

Who owns 193.176.31.198?

193.176.31.198 is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 193.176.31.192/26 block registered with RIPENCC.

Where is 193.176.31.198 located?

Geolocation places 193.176.31.198 in Amsterdam, The Netherlands. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 193.176.31.198 on a blacklist?

Yes. 193.176.31.198 is currently listed by 1 threat sources: FireHOL Level 3. DNS blacklists: 0 of 2 list it.

How do I report abuse from 193.176.31.198?

Send your log lines to the network's abuse contact, abuse@infrawat.ch, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/193.176.31.198

Guides for this IP