JPNE

BGP inherited

Cluster stats

Netblocks	6 · 147,450 IPv4 addresses
All fragments	9 blocks across 2 clusters
Cluster ID	211951232
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 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
103.2.8.0/22	JPNE	APNIC	ALLOCATED PORTABLE	● low
103.90.28.0/22	JPNE	APNIC	ALLOCATED PORTABLE	● low
106.72.0.0/15	JPNE	APNIC	ALLOCATED PORTABLE	● low
115.166.144.0/20	JPNE	APNIC	ALLOCATED PORTABLE	● low
193.82.64.0/19	JPNE	APNIC	ALLOCATED PORTABLE	● low
202.90.8.0/21	JPNE	APNIC	ALLOCATED PORTABLE	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “JPNE” — 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.

JPNE-JPNIC-JP-20110222 3 blocks

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.

JPnet-Infrastructure-and-hosting via VOe multimedia SA sub-allocation
XYJP via Yuan Xue sub-allocation
AACTJPNET sub-allocation
JNJXJPNET sub-allocation
JNJCJPNET sub-allocation
JNSLDJPNET sub-allocation
JNLMJPNET sub-allocation
JNYCJPNET sub-allocation

Network trust

what's this?

RPKI hygiene: D how networks compare →

33.3% of checked blocks have valid RPKI ROA coverage (2 of 6)

No discrepancies found among checked blocks.

NIC Handles

JNIC1-AP JNIC1-AP MAINT-JPNIC