bgpreport

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

16IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
16No ROA 16 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS129, seen from no peer

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% 67
155.27.62.0/23 No ROA None 672 100% 67
158.9.52.0/22 No ROA None 672 100% 67
205.67.43.0/24 No ROA None 672 100% 67
205.67.44.0/24 No ROA None 672 100% 67
205.67.45.0/24 No ROA None 672 100% 67
205.67.46.0/24 No ROA None 672 100% 67
205.77.65.0/24 No ROA None 672 100% 67
205.77.66.0/23 No ROA None 672 100% 67
205.77.68.0/22 No ROA None 672 100% 67
205.77.84.0/22 No ROA None 672 100% 67
205.77.86.0/24 No ROA None 672 100% 67
205.77.88.0/24 No ROA None 672 100% 67
205.77.96.0/23 No ROA None 672 100% 67
205.77.98.0/23 No ROA None 672 100% 67
214.29.56.0/22 No ROA None 671 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: none143.140.11.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none143.140.11.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none155.27.62.0/23No ROA covers it. Add a ROA for AS129, maxLength 23.672 of 673
Route object: none155.27.62.0/23No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none158.9.52.0/22No ROA covers it. Add a ROA for AS129, maxLength 22.672 of 673
Route object: none158.9.52.0/22No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.67.43.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.67.43.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.67.44.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.67.44.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.67.45.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.67.45.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.67.46.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.67.46.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.65.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.77.65.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.66.0/23No ROA covers it. Add a ROA for AS129, maxLength 23.672 of 673
Route object: none205.77.66.0/23No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.68.0/22No ROA covers it. Add a ROA for AS129, maxLength 22.672 of 673
Route object: none205.77.68.0/22No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.84.0/22No ROA covers it. Add a ROA for AS129, maxLength 22.672 of 673
Route object: none205.77.84.0/22No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.86.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.77.86.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.88.0/24No ROA covers it. Add a ROA for AS129, maxLength 24.672 of 673
Route object: none205.77.88.0/24No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.96.0/23No ROA covers it. Add a ROA for AS129, maxLength 23.672 of 673
Route object: none205.77.96.0/23No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none205.77.98.0/23No ROA covers it. Add a ROA for AS129, maxLength 23.672 of 673
Route object: none205.77.98.0/23No route object for it. Add a route object with origin AS129 in the RIR database for the space.672 of 673
ROA: none214.29.56.0/22No ROA covers it. Add a ROA for AS129, maxLength 22.671 of 673
Route object: none214.29.56.0/22No route object for it. Add a route object with origin AS129 in the RIR database for the space.671 of 673

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.