FansNET
Cluster stats
Netblocks11
All fragments 12 blocks across 2 clusters
Cluster ID193186611
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.147.192/32 FansNET PEERINGDB ASSIGNED ● high
195.60.92.90/32 FansNET PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:20:9294:1/128 FansNET PEERINGDB ASSIGNED ● high
2406:840:1f:1:0:20:9294:1/128 FansNET PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:20:9294:1/128 FansNET PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::46/128 FansNET PEERINGDB ASSIGNED ● high
2602:f93b:1a35:1311::90/128 FansNET PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:9::124/128 FansNET PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:16::13e/128 FansNET PEERINGDB ASSIGNED ● high
61.93.238.200/30 FANSNET APNIC ASSIGNED NON-PORTABLE ● low
2406:840:e840::/44 FansNET APNIC ALLOCATED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
72.7% of checked blocks have valid RPKI ROA coverage (8 of 11)
Possible discrepancies (1)

These blocks are registered to FansNET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2406:840:e840::/44 /44 authorized for AS209294 — Fan Zhang

NIC Handles

AS209294 CH134-AP FZ1113-AP FZ1113-AP MAINT-FANSNET MAINT-HK-CTI MAINT-NBDHM-CN SL113-AP