JDN-ID

BGP inherited
Cluster stats
Netblocks6 · 3,578 IPv4 addresses
Cluster ID206668592
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.251.4.0/24 JDN-ID APNIC ASSIGNED NON-PORTABLE ● low
45.251.5.0/24 JDN-ID APNIC ASSIGNED NON-PORTABLE ● low
45.251.6.0/24 JDN-ID APNIC ASSIGNED NON-PORTABLE ● low
45.251.7.0/24 JDN-ID APNIC ASSIGNED NON-PORTABLE ● low
103.161.238.0/23 JDN-ID APNIC ALLOCATED PORTABLE ● low
117.103.0.0/21 JDN-ID APNIC ALLOCATED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (4)

These blocks are registered to JDN-ID 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.

45.251.6.0/24 /24 authorized for AS38511 — PT Remala Abadi
45.251.4.0/24 /24 authorized for AS38511 — PT Remala Abadi
45.251.5.0/24 /24 authorized for AS38511 — PT Remala Abadi
45.251.7.0/24 /24 authorized for AS38511 — PT Remala Abadi

NIC Handles

BA96-AP MAINT-ID-TACHYON MNT-APJII-ID RK293-AP RP362-AP RP362-AP