IP abuse report101.36.108.202
101.36.108.202 is an IPv4 address located in Hong Kong, Hong Kong. It belongs to a network operated by UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED (AS135377). The address is listed by 6 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.
IP Information
- ISP / Organization
- UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED
- ASN
- AS135377 UCLOUD-HK-AS-AP
- ASN Domain
- ucloud.cn
- IP Range
- 101.36.96.0/19
- Regional Registry
- APNIC
- Connection Type
- Hosting / Datacenter
- Country
- Hong Kong (HK)
- Region / State
- Kowloon
- City
- Hong Kong 2 sources agree
- Time Zone
- Asia/Hong_Kong
- Abuse contact
- pn-wan@ucloud.cn 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- Coordinates
- 22.32, 114.17
- Network
- AS135377 UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED
The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.
Network Neighbourhood
101.36.108.0/247 of the 256 addresses in 101.36.108.0/24 are listed by our sources (2.7%).
Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.
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.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
Top reporter countries
- Germany1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
6In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 03:50
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IPsum (4+ lists) Aggregator | Single address | 2026-11-18 05:19 | 2026-11-20 03:4816 minutes ago |
| FireHOL Level 1 Aggregator | 101.36.96.0/19 | 2026-11-07 19:33 | 2026-11-20 03:4816 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Data-Shield IPv4 Blocklist | Single address | 2026-11-07 19:33 | 2026-11-20 03:4915 minutes ago |
| ShadowWhisperer Threats | Single address | 2026-11-07 19:34 | 2026-11-20 03:5014 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Spamhaus DROP | 101.36.96.0/19 | 2026-11-08 04:47 | 2026-11-19 09:1718 hours ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Emerging Threats Block IPs | 101.36.96.0/19 | 2026-11-07 19:32 | 2026-11-20 03:4718 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.
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.
- 14:02:07 ssh:22 101.36.108.202 login attempt root / ••••••
- 14:02:10 globalprotect:443 101.36.108.202 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 101.36.108.202 password spray Exchange OWA
- 14:02:16 netscaler:8443 101.36.108.202 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 1
Report This IPWho reported this address, when, and on what grounds.
-
ipdb-2eqxef Registered memberReason: Brute-Force
agressive scan, mailbox brutefroce, hacking
Reporters' IP addresses are never published — only the country they reported from.
Listing History
1The 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 101.36.108.202
Is 101.36.108.202 safe?
No. 101.36.108.202 scores 100/100 with strong, recent evidence of abuse (6 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 101.36.108.202?
101.36.108.202 is announced by AS135377 and operated by UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED. It sits in the 101.36.96.0/19 block registered with APNIC.
Where is 101.36.108.202 located?
Geolocation places 101.36.108.202 in Hong Kong, Hong Kong. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 101.36.108.202 on a blacklist?
Yes. 101.36.108.202 is currently listed by 6 threat sources: IPsum (4+ lists), Data-Shield IPv4 Blocklist, ShadowWhisperer Threats, Spamhaus DROP, Emerging Threats Block IPs, FireHOL Level 1.
How do I report abuse from 101.36.108.202?
Send your log lines to the network's abuse contact, pn-wan@ucloud.cn, 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/101.36.108.202