NTT IP Ranges
AS2914 is NTT's Global IP Network, the transit backbone that traded as NTT Communications and now sits under NTT DATA. The ARIN record makes the division plain: the ASN is named NTT-DATA-2914, it was registered on 7 December 1998, and the holder is NTT America, Inc. of 15809 Bear Creek Pkwy in Redmond, Washington rather than the Japanese retail business. Reassignment detail is not in ARIN at all - the record refers queries onward to NTT's own rwhois server at rwhois.gin.ntt.net on port 4321.
- Provider
- NTT
- Primary ASN
- AS2914
- Category
- Transit
- Headquarters
- Tokyo, Japan
- Announced IPv4 prefixes
- 1299
- Registry
- ARIN
Known IP ranges
These prefixes are currently announced to the global routing table by AS2914 (NTT-DATA-2914 - NTT America, Inc.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
204.200.0.0/14
199.236.0.0/14
204.0.0.0/14
204.170.0.0/15
198.106.0.0/15
204.142.0.0/15
198.64.0.0/15
207.56.0.0/15
153.254.0.0/15
198.138.0.0/15
2404:3600::/32
2001:218::/32
2001:418::/32 (IPv6)
What does an NTT IP mean in a privacy test?
Two very different things wear this ASN. NTT's backbone routers answer inside bb.gin.ntt.net with names that spell out where they sit, so 129.250.3.10 comes back as ae-5.a01.dllstx11.us.bb.gin.ntt.net, dllstx11 being the Dallas facility, and those are the addresses that appear mid-path in a traceroute rather than as an endpoint. The rest is space NTT allocated to itself decades ago, which is why a block like 204.200.0.0/14 reads in ARIN as a Direct Allocation to NTT America dated 2 December 1994 while ARIN holds no record of who is using any single address inside it. That is why an AS2914 address so rarely identifies who you are dealing with: ARIN answers with the wholesaler, and the only public route to the reassignment is NTT's own rwhois.
NTT runs its own routing registry and its own whois
Two pieces of NTT infrastructure are worth knowing before you trust a lookup. The first is rr.ntt.net, NTT's own Internet Routing Registry, which its published routing policy says runs in RPKI-aware mode and suppresses route and route6 IRR records that conflict with published RPKI ROAs; everything AS2914 announces is registered under the AS-SET AS2914:AS-GLOBAL, given in PeeringDB with its source prefix as NTTCOM::AS2914:AS-GLOBAL. The same policy states the prefix-length filters - /24 and shorter on IPv4, /48 and shorter on IPv6, in both directions with peers - and requires anyone announcing prefixes from Global IP Network equipment to publish and maintain a valid ROA.
The second is the rwhois server. The ARIN record for each of these blocks carries a ReferralServer of rwhois://rwhois.gin.ntt.net:4321, and that is where reassignment detail lives; ARIN itself shows only the parent, as a Direct Allocation to NTT America under handles such as NTTA-204-200 and NTTA-198-106. NTT also documents its BGP communities publicly, including the blackhole community 2914:666 for a /32 or /128 and the scoped variants 2914:660, 2914:661, 2914:663 and 2914:664, and runs a looking glass at gin.ntt.net/looking-glass/. What it does not publish is a geofeed or a public list of its points of presence - the PeeringDB record, which also marks the peering policy Restrictive, tells you to contact an NTT representative for the full POP list.
Backbone router, or a customer of a customer
NTT's own routers are the one thing on this network that identify themselves clearly. They answer inside bb.gin.ntt.net under a name that spells out the facility: 129.250.3.10 resolves to ae-5.a01.dllstx11.us.bb.gin.ntt.net, where ae-5 is the interface, a01 the router, dllstx11 the Dallas, Texas site and us the country. Any hostname in that zone is NTT equipment carrying traffic, and it is ordinary for one to sit in the middle of a path.
The legacy blocks are the opposite case. 204.200.0.0/14, registered to NTT America on 2 December 1994, and 198.106.0.0/15, registered on 31 January 2001, are ARIN Direct Allocations whose reverse zones NTT does operate - the SOA for the sampled zone is auth21.ns.gin.ntt.net - yet the addresses sampled inside them return NXDOMAIN, so the zone exists and the record simply is not there. An AS2914 address that is not a gin.ntt.net router therefore has no hostname to read and no ARIN entry beyond the parent allocation, and the rwhois server is the only public place the using organisation is named.
Related tools
Frequently asked questions
Is AS2914 the same network as NTT's Japanese consumer service?
No. AS2914 is the Global IP Network, registered with ARIN to NTT America, Inc. of Redmond, Washington under the ASN name NTT-DATA-2914. The Japanese retail ISP OCN runs on a separate number, AS4713, recorded in JPNIC under NTT DOCOMO BUSINESS, Inc.
How do I find out which customer is using an AS2914 address?
Through NTT's rwhois server. Every ARIN record for these blocks carries a ReferralServer of rwhois://rwhois.gin.ntt.net:4321, because ARIN holds only the parent allocation to NTT America and the reassignment records live on NTT's own server.
What does a hostname like ae-5.a01.dllstx11.us.bb.gin.ntt.net mean?
It is an NTT backbone router. The parts read as interface, router identifier, facility code and country, so dllstx11 is a Dallas, Texas site and us is the United States. Hostnames in the bb.gin.ntt.net zone are NTT's own equipment rather than customer machines.
Does NTT publish a geofeed?
No, and it does not publish a public list of its points of presence either - the PeeringDB record asks you to contact an NTT representative for the full list. The facility code inside a backbone router hostname is the closest thing to a public locator on this network.
Does NTT require RPKI on the routes it carries?
Yes. Its published routing policy states that parties announcing prefixes from Global IP Network equipment must publish and maintain a valid RPKI ROA, and that NTT will cease to announce prefixes without a valid covering ROA within three business days. Its routing registry at rr.ntt.net also runs RPKI-aware and suppresses route objects that conflict with published ROAs.