bgpreport

Network · data from 2026-11-12

AS518 DNIC-AS-00518 - United States Department of Defense (DoD)

Registry name: DNIC-AS-00518 - United States Department of Defense (DoD), US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS518, 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.

199.9.178.0/23 No ROA Other IRR onlyRADB 671 100% 69
199.9.178.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.179.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.180.0/22 No ROA Other IRR onlyRADB 671 100% 69
199.9.180.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.181.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.224.0/23 No ROA Other IRR onlyRADB 671 100% 69
199.9.226.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.228.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.229.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.230.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.231.0/24 No ROA Other IRR onlyRADB 671 100% 69
199.9.232.0/21 No ROA Other IRR onlyRADB 671 100% 69
199.9.240.0/21 No ROA Other IRR onlyRADB 671 100% 69
199.9.247.0/24 No ROA Other IRR onlyRADB 671 100% 69
2001:480:421::/48 Valid RIR databaseARIN, RADB 635 100% 70
2001:480:1610::/48 Valid RIR databaseARIN, RADB 635 100% 70

AS-SET

AS518 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: none15
  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
ROA: none199.9.178.0/23No ROA covers it. Add a ROA for AS518, maxLength 23.671 of 673
Route object: RIR199.9.178.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.178.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.178.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.179.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.179.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.180.0/22No ROA covers it. Add a ROA for AS518, maxLength 22.671 of 673
Route object: RIR199.9.180.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.180.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.180.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.181.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.181.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.224.0/23No ROA covers it. Add a ROA for AS518, maxLength 23.671 of 673
Route object: RIR199.9.224.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.226.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.226.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.228.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.228.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.229.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.230.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.230.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.231.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.231.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.232.0/21No ROA covers it. Add a ROA for AS518, maxLength 21.671 of 673
Route object: RIR199.9.232.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.240.0/21No ROA covers it. Add a ROA for AS518, maxLength 21.671 of 673
Route object: RIR199.9.240.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.9.247.0/24No ROA covers it. Add a ROA for AS518, maxLength 24.671 of 673
Route object: RIR199.9.247.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS518 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.