Nippon Telegraph and Telephone Corporation
NTTV6NET
Cluster stats
Netblocks14
Cluster ID193097107
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.16.178.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● high
2001:200:400::/40 NTTV6NET APNIC ASSIGNED NON-PORTABLE ● high
192.26.93.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.162.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.163.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.164.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.165.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.174.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.175.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.176.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.177.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.178.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.47.179.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low
192.172.237.0/24 NTTV6NET APNIC ASSIGNED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
7.1% of checked blocks have valid RPKI ROA coverage (1 of 14)
RPKI-inferred operator WIDE Project
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-JP-NTTV6NET MAINT-JP-WIDE MAINT-JPNIC SM503-AP SM503-AP TF19-AP TF19-AP