Network · data from 2026-11-12
AS19809 NTT Global Networks (AS19809)
Registry name: ASNBLK-VTLA2 - NTT Global Networks Incorporated, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19809, 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.121.0/24 | No ROA | Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 69.26.55.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 119.31.174.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 207.179.28.0/24 | No ROA | Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 74.220.105.0/24 | No ROA | Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH | 670 100% |
| 119.31.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS19809: AS19809. 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 (AS19809 isn't in the set, or no route object for AS19809 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 | AS19809 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS19809 | A single AS number, not a set: AS19809 (this network), 8 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 12 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.254.121.0/24 | No ROA covers it. Add a ROA for AS19809, maxLength 24. |
| Route object: RIR | 64.254.121.0/24 | Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 69.26.55.0/24 | No ROA covers it. Add a ROA for AS19809, maxLength 24. |
| Route object: RIR | 69.26.55.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 119.31.174.0/24 | No ROA covers it. Add a ROA for AS19809, maxLength 24. |
| Route object: RIR | 119.31.174.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 207.179.28.0/24 | No ROA covers it. Add a ROA for AS19809, maxLength 24. |
| Route object: RIR | 207.179.28.0/24 | Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 74.220.105.0/24 | No ROA covers it. Add a ROA for AS19809, maxLength 24. |
| Route object: RIR | 74.220.105.0/24 | Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19809 whose prefix no peer sees AS19809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.197.206.0/23 | RADB, RIPE-NONAUTH | No ROA |
| 207.179.0.0/19 | 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.