FENGYE NETWORKS LIMITED

Data as of 2026-11-01
BGP inherited
This organisation
Netblocks6 · 18,432 IPv4 addresses
IPv6 3 prefixes (largest 2a14:4900::/29)
Record ID259711986
RegistryAPNIC
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.219.192.0/22 FENGYE NETWORKS LIMITED APNIC ALLOCATED PORTABLE ● low
185.241.40.0/22 FENGYE NETWORKS LIMITED RIPE ALLOCATED PA ● low
209.33.128.0/18 FENGYE NETWORKS LIMITED RIPE ALLOCATED PA ● low
2001:df2:4600::/48 FENGYE NETWORKS LIMITED APNIC ASSIGNED PORTABLE ● low
2401:7d20::/32 FENGYE NETWORKS LIMITED APNIC ALLOCATED PORTABLE ● low
2a14:4900::/29 FENGYE NETWORKS LIMITED RIPE ALLOCATED-BY-RIR ● low

IPv6 ranges (3)

Footprint over time

17 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-11-01

Network trust

what's this?
RPKI hygiene: F how networks compare →
16.7% of checked blocks have valid RPKI ROA coverage (1 of 6)
Possible discrepancies (1)

These blocks are registered to FENGYE NETWORKS LIMITED 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.

185.241.40.0/22 /22 authorized for AS63150 — BAGE CLOUD LLC

NIC Handles

AF507-AP APNIC-HM DUMY-RIPE DUMY-RIPE FNLA2-AP FNLA2-AP ORG-FNL1-AP ORG-FNL20-RIPE RIPE-NCC-HM-MNT hk-fengyecom-1-mnt