Network · data from 2026-11-12
AS63306 TOUCHTONE-LA
Registry name: TOUCHTONE-LA - TouchTone Communications, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63306, 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.
| 66.207.190.0/24 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 165.254.46.0/24 | Valid | Other IRR onlyNTTCOM | 670 100% |
| 192.40.216.0/24 | Valid | Other IRR onlyNTTCOM | 669 99% |
| 165.254.166.0/24 | Valid | Other IRR onlyNTTCOM | 157 23% |
AS-SET
PeeringDB's irr_as_set for AS63306: AS-SET. 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 (AS63306 isn't in the set, or no route object for AS63306 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 | AS63306 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET | RADB | 0 | 1 | No | 4 |
| AFRINIC (also) | 1 | 1 | No | 4 | |
| ARIN (also) | 0 | 1 | No | 4 | |
| RIPE (also)1 member set in no database: AS200105:AS-HK | 38 | 15 | No | 4 |
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 18 are in fix.csv.
- ROA: none1
- Route object: RIR4
- AS-SET: own ASN1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.207.190.0/24 | No ROA covers it. Add a ROA for AS63306, maxLength 24. |
| Route object: RIR | 66.207.190.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 165.254.46.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 192.40.216.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 165.254.166.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-SET | AS63306 isn't in AS-SET (RADB) once expanded. Add AS63306 to it. |
Route objects not announced
Route objects with origin AS63306 whose prefix no peer sees AS63306 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 140.174.26.0/23 | NTTCOM | Valid |
| 140.174.30.0/24 | NTTCOM | Valid |
| 140.174.37.0/24 | NTTCOM | Valid |
| 165.254.21.16/29 | NTTCOM | Valid |
| 165.254.26.224/29 | NTTCOM | Valid |
| 165.254.30.0/24 | NTTCOM | Valid |
| 165.254.104.0/24 | NTTCOM | Valid |
| 172.83.126.0/24 | NTTCOM | Valid |
| 192.35.181.0/24 | NTTCOM | No ROA |
| 192.64.199.0/24 | NTTCOM | No ROA |
| 192.156.240.0/24 | ARIN | Valid |
| 216.73.185.0/24 | 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.