bgpreport

Network · data from 2026-11-12

AS368 DNIC-ASBLK-00306-00371 - United States Department of Defense (DoD)

Registry name: DNIC-ASBLK-00306-00371 - United States Department of Defense (DoD), US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS368, 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.
55.42.0.0/16 No ROA None 671 100% 67
55.42.96.0/22 No ROA None 671 100% 67
55.87.0.0/16 No ROA None 671 100% 67
55.87.96.0/22 No ROA None 671 100% 67
55.87.100.0/24 No ROA None 671 100% 67
55.87.101.0/24 No ROA None 671 100% 67
55.87.255.0/24 No ROA None 671 100% 67
2608:10a:4700::/40 No ROA None 636 100% 67

AS-SET

AS368 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none55.42.0.0/16No ROA covers it. Add a ROA for AS368, maxLength 16.671 of 673
Route object: none55.42.0.0/16No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.42.96.0/22No ROA covers it. Add a ROA for AS368, maxLength 22.671 of 673
Route object: none55.42.96.0/22No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.87.0.0/16No ROA covers it. Add a ROA for AS368, maxLength 16.671 of 673
Route object: none55.87.0.0/16No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.87.96.0/22No ROA covers it. Add a ROA for AS368, maxLength 22.671 of 673
Route object: none55.87.96.0/22No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.87.100.0/24No ROA covers it. Add a ROA for AS368, maxLength 24.671 of 673
Route object: none55.87.100.0/24No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.87.101.0/24No ROA covers it. Add a ROA for AS368, maxLength 24.671 of 673
Route object: none55.87.101.0/24No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none55.87.255.0/24No ROA covers it. Add a ROA for AS368, maxLength 24.671 of 673
Route object: none55.87.255.0/24No route object for it. Add a route object with origin AS368 in the RIR database for the space.671 of 673
ROA: none2608:10a:4700::/40No ROA covers it. Add a ROA for AS368, maxLength 40.636 of 636
Route object: none2608:10a:4700::/40No route object for it. Add a route object with origin AS368 in the RIR database for the space.636 of 636

Route objects not announced

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