JINYU

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
180.166.117.20/30 JINYU APNIC ASSIGNED NON-PORTABLE ● high
180.168.40.244/30 JINYU APNIC ASSIGNED NON-PORTABLE ● high
180.168.51.132/30 JINYU APNIC ASSIGNED NON-PORTABLE ● high
180.168.82.92/30 JINYU APNIC ASSIGNED NON-PORTABLE ● high
202.108.135.0/26 JINYU-CO APNIC ASSIGNED NON-PORTABLE ● high
218.80.196.84/30 JINYU-CO APNIC ASSIGNED NON-PORTABLE ● high
218.80.203.24/30 JINYU-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.51.68/30 JINYU-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JINYU” — 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: B how networks compare →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP BQ50-AP BQ50-AP CQS6-AP CQS6-AP CQS7-AP CQS7-AP LF834-AP LF834-AP LJR5-AP LJR5-AP MAINT-CHINANET-SH +7 more