Network · data from 2026-11-12
AS129 DNIC-AS-00129 - United States Department of Defense (DoD)
Registry name: DNIC-AS-00129 - United States Department of Defense (DoD), US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS129, 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.
| 143.140.11.0/24 | No ROA | None | 672 100% |
| 155.27.62.0/23 | No ROA | None | 672 100% |
| 158.9.52.0/22 | No ROA | None | 672 100% |
| 205.67.43.0/24 | No ROA | None | 672 100% |
| 205.67.44.0/24 | No ROA | None | 672 100% |
| 205.67.45.0/24 | No ROA | None | 672 100% |
| 205.67.46.0/24 | No ROA | None | 672 100% |
| 205.77.65.0/24 | No ROA | None | 672 100% |
| 205.77.66.0/23 | No ROA | None | 672 100% |
| 205.77.68.0/22 | No ROA | None | 672 100% |
| 205.77.84.0/22 | No ROA | None | 672 100% |
| 205.77.86.0/24 | No ROA | None | 672 100% |
| 205.77.88.0/24 | No ROA | None | 672 100% |
| 205.77.96.0/23 | No ROA | None | 672 100% |
| 205.77.98.0/23 | No ROA | None | 672 100% |
| 214.29.56.0/22 | No ROA | None | 671 100% |
AS-SET
AS129 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 32 are in fix.csv.
- ROA: none16
- Route object: none16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 143.140.11.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 143.140.11.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 155.27.62.0/23 | No ROA covers it. Add a ROA for AS129, maxLength 23. |
| Route object: none | 155.27.62.0/23 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 158.9.52.0/22 | No ROA covers it. Add a ROA for AS129, maxLength 22. |
| Route object: none | 158.9.52.0/22 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.67.43.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.67.43.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.67.44.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.67.44.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.67.45.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.67.45.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.67.46.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.67.46.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.65.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.77.65.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.66.0/23 | No ROA covers it. Add a ROA for AS129, maxLength 23. |
| Route object: none | 205.77.66.0/23 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.68.0/22 | No ROA covers it. Add a ROA for AS129, maxLength 22. |
| Route object: none | 205.77.68.0/22 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.84.0/22 | No ROA covers it. Add a ROA for AS129, maxLength 22. |
| Route object: none | 205.77.84.0/22 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.86.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.77.86.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.88.0/24 | No ROA covers it. Add a ROA for AS129, maxLength 24. |
| Route object: none | 205.77.88.0/24 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.96.0/23 | No ROA covers it. Add a ROA for AS129, maxLength 23. |
| Route object: none | 205.77.96.0/23 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 205.77.98.0/23 | No ROA covers it. Add a ROA for AS129, maxLength 23. |
| Route object: none | 205.77.98.0/23 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
| ROA: none | 214.29.56.0/22 | No ROA covers it. Add a ROA for AS129, maxLength 22. |
| Route object: none | 214.29.56.0/22 | No route object for it. Add a route object with origin AS129 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS129 is announced.
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.