IDCLLC-JP

BGP inherited
Cluster stats
Netblocks8 · 2,040 IPv4 addresses
Cluster ID210298328
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
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
45.124.220.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
45.124.221.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
45.124.222.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
45.124.223.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
103.248.68.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
103.248.69.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
103.248.70.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low
103.248.71.0/24 IDCLLC-JP APNIC ALLOCATED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
RPKI-inferred operator BEKKOAME INTERNET INC.
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AI749-AP ILA3-AP ILA3-AP MAINT-IDCLLC-JP