Network · data from 2026-11-12
AS8119 DTN-AS - DTN, LLC
Registry name: DTN-AS - DTN, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8119, 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.112.145.0/24 | No ROA | Nonecovered by 66.112.144.0/20 | 672 100% |
| 207.252.127.0/24 | No ROA | None | 672 100% |
| 66.112.144.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.112.146.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 66.112.151.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 67.97.112.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 208.3.212.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 66.112.147.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 66.112.149.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 66.112.152.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 66.112.154.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 66.112.156.0/24 | Valid | RIR databaseARIN | 672 100% |
| 69.41.208.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 69.41.209.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 69.41.210.0/24 | Valid | RIR databaseARIN | 672 100% |
| 69.41.216.0/24 | Valid | RIR databaseARIN | 672 100% |
| 69.41.217.0/24 | Valid | RIR databaseARIN | 672 100% |
| 69.41.218.0/24 | Valid | RIR databaseARIN | 672 100% |
| 69.41.222.0/24 | Valid | RIR databaseARIN | 672 100% |
| 66.112.148.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 66.112.150.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 66.112.153.0/24 | Valid | RIR databaseARIN | 671 100% |
| 69.41.213.0/24 | Valid | RIR databaseARIN | 671 100% |
| 69.41.223.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS8119 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 18 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.112.145.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: none | 66.112.145.0/24 | No route object for it. A route object for 66.112.144.0/20 with origin AS8119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8119 in the RIR database for the space. |
| ROA: none | 207.252.127.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: none | 207.252.127.0/24 | No route object for it. Add a route object with origin AS8119 in the RIR database for the space. |
| ROA: none | 66.112.144.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: RIR | 66.112.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.112.146.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: RIR | 66.112.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.112.151.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: RIR | 66.112.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 67.97.112.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: RIR | 67.97.112.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.3.212.0/24 | No ROA covers it. Add a ROA for AS8119, maxLength 24. |
| Route object: RIR | 208.3.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8119 whose prefix no peer sees AS8119 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.112.144.0/20 | RADB | No ROA |
| 66.112.155.0/24 | ARIN | Valid |
| 69.41.208.0/20 | RADB | No ROA |
| 69.41.212.0/24 | ARIN | Valid |
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.