Network · data from 2026-11-12
AS19806 NTT Global Networks (AS19806)
Registry name: ASNBLK-VTLA2 - NTT Global Networks Incorporated, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19806, 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.119.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 69.26.46.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 69.26.53.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 77.247.9.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 77.247.10.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 77.247.11.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS19806: AS19806. 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 (AS19806 isn't in the set, or no route object for AS19806 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 | AS19806 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS19806 | A single AS number, not a set: AS19806 (this network), 14 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 14 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.254.119.0/24 | No ROA covers it. Add a ROA for AS19806, maxLength 24. |
| Route object: RIR | 64.254.119.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 69.26.46.0/24 | No ROA covers it. Add a ROA for AS19806, maxLength 24. |
| Route object: RIR | 69.26.46.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 69.26.53.0/24 | No ROA covers it. Add a ROA for AS19806, maxLength 24. |
| Route object: RIR | 69.26.53.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 AS19806 whose prefix no peer sees AS19806 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.235.108.0/24 | RIPE | Valid |
| 69.26.52.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 131.197.142.0/23 | RIPE-NONAUTH | No ROA |
| 195.130.210.0/24 | RADB, RIPE | No ROA |
| 212.11.83.0/24 | RIPE | Valid |
| 212.11.85.0/24 | RIPE | Valid |
| 212.11.86.0/24 | RIPE | Valid |
| 2a01:8680::/32 | RIPE | 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.