JPNICNET
BGP inherited
Cluster stats
| Netblocks | 6 · 766 IPv4 addresses |
| Cluster ID | 206474270 |
| 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.131.194.0/23 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
| 192.41.192.0/24 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
| 2001:df2:da00::/48 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
| 2001:df4:6680::/48 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
| 2001:df4:b480::/48 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
| 2001:df7:8380::/48 | JPNICNET | APNIC | ASSIGNED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(2 of 6)
RPKI-inferred operator
Japan Network Information Center
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
JNIC1-AP
JNIC1-AP
MAINT-JPNIC