Network · data from 2026-11-12
AS26342 DTTS-ASN - Deloitte Touche Tohmatsu Services, Inc.
Registry name: DTTS-ASN - Deloitte Touche Tohmatsu Services, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26342, 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.194.128.0/20 | No ROA | None | 673 100% |
| 170.194.136.0/21 | No ROA | None | 673 100% |
| 2620:119:e010::/44 | No ROA | None | 480 75% |
| 2620:119:e010::/48 | No ROA | None | 480 75% |
| 2620:119:e000::/42 | No ROA | None | 434 68% |
| 170.194.168.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 170.194.134.0/23 | Valid | RIR databaseARIN | 673 100% |
| 170.194.134.0/24 | Valid | RIR databaseARIN | 673 100% |
| 170.194.135.0/24 | Valid | RIR databaseARIN | 673 100% |
| 2620:1bd:4000::/36 | Valid | RIR databaseARIN | 635 100% |
AS-SET
AS26342 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 17 are in fix.csv.
- ROA: none6
- Route object: none5
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.194.128.0/20 | No ROA covers it. Add a ROA for AS26342, maxLength 20. |
| Route object: none | 170.194.128.0/20 | No route object for it. Add a route object with origin AS26342 in the RIR database for the space. |
| ROA: none | 170.194.136.0/21 | No ROA covers it. Add a ROA for AS26342, maxLength 21. |
| Route object: none | 170.194.136.0/21 | No route object for it. Add a route object with origin AS26342 in the RIR database for the space. |
| ROA: none | 2620:119:e010::/44 | No ROA covers it. Add a ROA for AS26342, maxLength 44. |
| Route object: none | 2620:119:e010::/44 | No route object for it. Add a route object with origin AS26342 in the RIR database for the space. |
| ROA: none | 2620:119:e010::/48 | No ROA covers it. Add a ROA for AS26342, maxLength 48. |
| Route object: none | 2620:119:e010::/48 | No route object for it. Add a route object with origin AS26342 in the RIR database for the space. |
| ROA: none | 2620:119:e000::/42 | No ROA covers it. Add a ROA for AS26342, maxLength 42. |
| Route object: none | 2620:119:e000::/42 | No route object for it. Add a route object with origin AS26342 in the RIR database for the space. |
| ROA: none | 170.194.168.0/21 | No ROA covers it. Add a ROA for AS26342, maxLength 21. |
| Route object: RIR | 170.194.168.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26342 whose prefix no peer sees AS26342 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.245.148.0/22 | RADB | No ROA |
| 170.194.152.0/21 | RADB | No ROA |
| 170.194.160.0/21 | ARIN | No ROA |
| 170.194.176.0/20 | RADB | No ROA |
| 170.194.200.0/21 | ARIN | 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.