Network · data from 2026-11-12
AS10217 NTT Indonesia
Registry name: NTT-NET-ID-AS - PT. NTT Indonesia, ID · PeeringDB
20IPv4 routes
100.0% RPKI valid · 55.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
9 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
32Route objects not announced
registered with origin AS10217, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS10217, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 119.11.130.0/23 | Valid | Nonecovered by 119.11.128.0/18 | 672 100% |
| 119.11.130.0/24 | Valid | Nonecovered by 119.11.128.0/18 | 672 100% |
| 119.11.132.0/24 | Valid | Nonecovered by 119.11.128.0/18 | 672 100% |
| 119.11.181.0/24 | Valid | Nonecovered by 119.11.128.0/18 | 672 100% |
| 119.11.200.0/24 | Valid | Nonecovered by 119.11.192.0/18 | 672 100% |
| 119.11.209.0/24 | Valid | Nonecovered by 119.11.192.0/18 | 672 100% |
| 119.11.217.0/24 | Valid | Nonecovered by 119.11.192.0/18 | 672 100% |
| 119.11.218.0/24 | Valid | Nonecovered by 119.11.192.0/18 | 672 100% |
| 119.11.196.0/24 | Valid | Nonecovered by 119.11.192.0/18 | 36 5%low visibility |
| 119.11.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 119.11.128.0/18 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 119.11.192.0/18 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 202.171.0.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.171.0.0/20 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 202.171.2.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 202.171.16.0/20 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 202.171.27.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.171.9.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2404:c8::/32 | Valid | Other IRR onlyNTTCOM, RADB | 634 100% |
| 119.11.250.0/24 | Valid | Other IRR onlyNTTCOM | 156 23% |
| 119.11.251.0/24 | Valid | Other IRR onlyNTTCOM | 156 23% |
AS-SET
PeeringDB's irr_as_set for AS10217: AS-NTTNETID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS10217 isn't in the set, or no route object for AS10217 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS10217 in it | Not covered |
|---|---|---|---|---|---|
| AS-NTTNETID | NTTCOM13 member sets in no database: AS-BCMEDIA, AS-BOSTI, AS-KDINDO, AS-LINTASDATA-AS-ID, AS-NETCITI … | 676 | 89 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 66 are in fix.csv.
- Route object: none9
- Route object: RIR12
- AS-SET: missing member13
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 119.11.130.0/23 | No route object for it. A route object for 119.11.128.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.130.0/24 | No route object for it. A route object for 119.11.128.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.132.0/24 | No route object for it. A route object for 119.11.128.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.181.0/24 | No route object for it. A route object for 119.11.128.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.200.0/24 | No route object for it. A route object for 119.11.192.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.209.0/24 | No route object for it. A route object for 119.11.192.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.217.0/24 | No route object for it. A route object for 119.11.192.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.218.0/24 | No route object for it. A route object for 119.11.192.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: none | 119.11.196.0/24 | No route object for it. A route object for 119.11.192.0/18 with origin AS10217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10217 in the RIR database for the space. |
| Route object: RIR | 119.11.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.11.128.0/18 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 119.11.192.0/18 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.0.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.0.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.16.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.27.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.171.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2404:c8::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.11.250.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 119.11.251.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS-BCMEDIA; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS-BOSTI; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS-KDINDO; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS-LINTASDATA-AS-ID; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS-NETCITI; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS135454:AS-AXAGOID; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS150196:AS-ARTHALOKA-ID; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS150238:AS-SHARTEL; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS150249:AS-ATHARVA; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS150501:AS-HCI; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS150552:AS-BAROKAHNET; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS63883:AS-CLOUDSERVERS; no IRR database read has it. |
| AS-SET: missing member | AS-NTTNETID | AS-NTTNETID (NTTCOM) lists AS9251:AS-INTERLINK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS10217 whose prefix no peer sees AS10217 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.171.0.0/22 | NTTCOM | Valid |
| 202.171.0.0/24 | RADB | Valid |
| 202.171.1.0/24 | RADB | Valid |
| 202.171.3.0/24 | RADB | Valid |
| 202.171.4.0/24 | RADB | Valid |
| 202.171.5.0/24 | RADB | Valid |
| 202.171.6.0/24 | RADB | Valid |
| 202.171.7.0/24 | RADB | Valid |
| 202.171.10.0/24 | RADB | Valid |
| 202.171.11.0/24 | RADB | Valid |
| 202.171.12.0/24 | RADB | Valid |
| 202.171.13.0/24 | RADB | Valid |
| 202.171.14.0/24 | RADB | Valid |
| 202.171.15.0/24 | NTTCOM, RADB | Valid |
| 202.171.16.0/24 | RADB | Valid |
| 202.171.17.0/24 | RADB | Valid |
| 202.171.18.0/24 | NTTCOM, RADB | Valid |
| 202.171.19.0/24 | RADB | Valid |
| 202.171.20.0/24 | RADB | Valid |
| 202.171.21.0/24 | RADB | Valid |
| 202.171.22.0/24 | RADB | Valid |
| 202.171.23.0/24 | RADB | Valid |
| 202.171.24.0/24 | RADB | Valid |
| 202.171.25.0/24 | RADB | Valid |
| 202.171.26.0/24 | RADB | Valid |
| 202.171.28.0/24 | RADB | Valid |
| 202.171.29.0/24 | RADB | Valid |
| 202.171.30.0/24 | RADB | Valid |
| 202.171.31.0/24 | RADB | Valid |
| 2001:df0:98::/48 | NTTCOM | No ROA |
| 2402:fc00::/32 | NTTCOM | No ROA |
| 2404:1400::/32 | NTTCOM | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.