JLDS

BGP inherited
Cluster stats
Netblocks9
Cluster ID210294935
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 22 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.159.128/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
116.228.159.208/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.240/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
116.236.253.224/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
222.66.83.200/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
222.66.83.208/29 JLDS APNIC ASSIGNED NON-PORTABLE ● high
222.68.109.132/30 JLDS APNIC ASSIGNED NON-PORTABLE ● high
60.210.168.212/30 JLDS APNIC ASSIGNED NON-PORTABLE ● low
220.231.49.224/29 JLDS APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
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.
  • VAJLDSTROJ-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • WFJLDS via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

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

NIC Handles

AC1591-AP CH471-AP DS95-AP DS95-AP HB124-AP HB124-AP HB353-AP HB353-AP HB355-AP HB355-AP HB356-AP HB356-AP +10 more