Network · data from 2026-11-12
AS18488 NTT Global Networks (AS18488)
Registry name: VTLA - NTT Global Networks Incorporated, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18488, 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.
| 64.254.116.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 69.26.43.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 119.31.166.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 74.220.97.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS18488: AS18488. 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 (AS18488 isn't in the set, or no route object for AS18488 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 | AS18488 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS18488 | A single AS number, not a set: AS18488 (this network), 9 route objects. | |||||
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 13 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.254.116.0/24 | No ROA covers it. Add a ROA for AS18488, maxLength 24. |
| Route object: RIR | 64.254.116.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 69.26.43.0/24 | No ROA covers it. Add a ROA for AS18488, maxLength 24. |
| Route object: RIR | 69.26.43.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 119.31.166.0/24 | No ROA covers it. Add a ROA for AS18488, maxLength 24. |
| Route object: RIR | 119.31.166.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 74.220.97.0/24 | No ROA covers it. Add a ROA for AS18488, maxLength 24. |
| Route object: RIR | 74.220.97.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18488 whose prefix no peer sees AS18488 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.62.4.0/22 | RADB, RIPE-NONAUTH | No ROA |
| 167.191.152.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 167.191.252.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 170.225.184.0/22 | RADB | No ROA |
| 192.86.38.0/24 | RADB | 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.