DICNET

BGP inherited
Cluster stats
Netblocks8 · 65,616 IPv4 addresses
Registered in India (7) · Japan (1)
Cluster ID210209226
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 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
124.30.39.0 – 124.30.39.11 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.118.140 – 124.30.118.163 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.152.0 – 124.30.152.11 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.176.12 – 124.30.176.23 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.181.192 – 124.30.181.203 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.198.152 – 124.30.198.163 DICNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.202.92/30 DICNET APNIC ASSIGNED NON-PORTABLE ● low
159.211.0.0/16 DICNET APNIC ALLOCATED 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.

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

HS51-AP HS51-AP JK26-AP JK26-AP MAINT-IN-IRINN MAINT-IN-SIFY MAINT-JPNIC