IP abuse report202.166.198.191

Suspicious Residential IPv4 Nepal AS17501

202.166.198.191 is an IPv4 address located in Patan (Jāwalākhel), Nepal. It belongs to a network operated by WorldLink Communications (AS17501). The address is listed by 1 of the threat-intelligence sources we track and carries a confidence score of 50/100. No community reports have been filed for it yet.

Last updated Listing sources 1 Community Reports 0 How the score works
Listing sources1
Community Reports0
Distinct Reporters0
Last seen 34 minutes ago

IP Information

ISP / Organization
WorldLink Communications
ASN
AS17501 WLINK-NEPAL-AS-AP
IP Range
202.166.198.0/23
Regional Registry
APNIC
Connection Type
Residential
Country
Nepal (NP)
Region / State
Bagmati Province
City
Patan (Jāwalākhel)
Time Zone
Unknown
Abuse contact
abuse.enterprise@worldlink.com.np 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
Patan (Jāwalākhel) Bagmati Province, Nepal
Coordinates
27.67, 85.31
Network
AS17501 WorldLink Communications
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

202.166.198.0/24

2 of the 256 addresses in 202.166.198.0/24 are listed by our sources (0.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
202.166.198.189

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

Blacklist Matches

1

In our pool since: 2026-11-16 05:17 (3 days ago) · Last confirmed: 2026-11-20 03:48

SSH Brute Force 1
SourceScopeFirst seenConfirmed
James Brine Brute-Force Hosts Single address 2026-11-16 05:17 2026-11-20 04:184 minutes 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 202.166.198.191 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 202.166.198.191 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 202.166.198.191 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 202.166.198.191 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 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

1
Added to the pool
3 days ago
2026-11-16 05:22

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 202.166.198.191

Is 202.166.198.191 safe?

202.166.198.191 scores 50/100 from several independent signals (1 source). Rate-limit or challenge its traffic and review your logs for it.

Who owns 202.166.198.191?

202.166.198.191 is announced by AS17501 and operated by WorldLink Communications. It sits in the 202.166.198.0/23 block registered with APNIC.

Where is 202.166.198.191 located?

Geolocation places 202.166.198.191 in Patan (Jāwalākhel), Nepal. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 202.166.198.191 on a blacklist?

Yes. 202.166.198.191 is currently listed by 1 threat sources: James Brine Brute-Force Hosts.

How do I report abuse from 202.166.198.191?

Send your log lines to the network's abuse contact, abuse.enterprise@worldlink.com.np, 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/202.166.198.191

Guides for this IP