Network · data from 2026-11-12
AS14201 TELETECH - TeleTech Holdings, Inc
Registry name: TELETECH - TeleTech Holdings, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14201, 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.
| 170.65.88.0/24 | No ROA | Nonecovered by 170.65.88.0/23 | 672 100% |
| 170.65.89.0/24 | No ROA | Nonecovered by 170.65.88.0/23 | 672 100% |
| 170.65.32.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.65.101.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.65.128.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.65.129.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.65.172.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.65.237.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS14201 isn't in PeeringDB, where networks name their AS-SET.
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 30 are in fix.csv.
- ROA: none8
- Route object: none2
- Route object: RIR6
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.65.88.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: none | 170.65.88.0/24 | No route object for it. A route object for 170.65.88.0/23 with origin AS14201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14201 in the RIR database for the space. |
| ROA: none | 170.65.89.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: none | 170.65.89.0/24 | No route object for it. A route object for 170.65.88.0/23 with origin AS14201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14201 in the RIR database for the space. |
| ROA: none | 170.65.32.0/22 | No ROA covers it. Add a ROA for AS14201, maxLength 22. |
| Route object: RIR | 170.65.32.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.65.101.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: RIR | 170.65.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.65.128.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: RIR | 170.65.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.65.129.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: RIR | 170.65.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.65.172.0/22 | No ROA covers it. Add a ROA for AS14201, maxLength 22. |
| Route object: RIR | 170.65.172.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.65.237.0/24 | No ROA covers it. Add a ROA for AS14201, maxLength 24. |
| Route object: RIR | 170.65.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14201 whose prefix no peer sees AS14201 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.65.0.0/16 | RADB | No ROA |
| 170.65.88.0/23 | RADB | No ROA |
| 170.65.95.0/24 | RADB | No ROA |
| 170.65.100.0/23 | RADB | No ROA |
| 170.65.100.0/24 | RADB | No ROA |
| 170.65.128.0/23 | RADB | No ROA |
| 170.65.150.0/24 | NTTCOM | No ROA |
| 170.65.170.0/24 | NTTCOM, RADB | No ROA |
| 170.65.188.0/24 | RADB | No ROA |
| 170.65.200.0/24 | RADB | No ROA |
| 170.65.201.0/24 | RADB | No ROA |
| 170.65.203.0/24 | RADB | No ROA |
| 170.65.217.0/24 | NTTCOM, RADB | No ROA |
| 170.65.218.0/24 | NTTCOM, 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.