YILONG

BGP inherited
Cluster stats
Netblocks8
All fragments 16 blocks across 7 clusters
Cluster ID210260906
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 18 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.32.191.104/30 YILONG-CO APNIC ASSIGNED NON-PORTABLE ● high
116.236.214.24/30 YILONG APNIC ASSIGNED NON-PORTABLE ● high
116.247.74.184/30 YILONG APNIC ASSIGNED NON-PORTABLE ● high
116.247.100.128/29 YILONG APNIC ASSIGNED NON-PORTABLE ● high
180.168.58.240/30 YILONG APNIC ASSIGNED NON-PORTABLE ● high
180.168.66.16/30 YILONG APNIC ASSIGNED NON-PORTABLE ● high
180.169.38.192/29 YILONG APNIC ASSIGNED NON-PORTABLE ● high
222.68.179.228/30 YILONG-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “YILONG” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP DY632-AP DY632-AP MAINT-CHINANET-SH SJ976-AP SJ976-AP SM1085-AP SM1085-AP SM1131-AP SM1131-AP SM1167-AP SM1167-AP +6 more