Network · data from 2026-11-12

AS355 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

3IPv4 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

4No ROA 4 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS355, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS355, 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.46.0.0/16	No ROA	None	671 100%	67
55.46.0.0/17	No ROA	None	671 100%	67
55.46.128.0/17	No ROA	None	671 100%	67
2608:18a:5200::/40	No ROA	None	636 100%	67

AS-SET

AS355 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 8 are in fix.csv.

ROA: none4
Route object: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	55.46.0.0/16	No ROA covers it. Add a ROA for AS355, maxLength 16.	671 of 673
Route object: none	55.46.0.0/16	No route object for it. Add a route object with origin AS355 in the RIR database for the space.	671 of 673
ROA: none	55.46.0.0/17	No ROA covers it. Add a ROA for AS355, maxLength 17.	671 of 673
Route object: none	55.46.0.0/17	No route object for it. Add a route object with origin AS355 in the RIR database for the space.	671 of 673
ROA: none	55.46.128.0/17	No ROA covers it. Add a ROA for AS355, maxLength 17.	671 of 673
Route object: none	55.46.128.0/17	No route object for it. Add a route object with origin AS355 in the RIR database for the space.	671 of 673
ROA: none	2608:18a:5200::/40	No ROA covers it. Add a ROA for AS355, maxLength 40.	636 of 636
Route object: none	2608:18a:5200::/40	No route object for it. Add a route object with origin AS355 in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

55.46.0.0/16

No ROA covers it. Add a ROA for AS355, maxLength 16.

671 of 673

Route object: none

55.46.0.0/16

No route object for it. Add a route object with origin AS355 in the RIR database for the space.

671 of 673

ROA: none

55.46.0.0/17

No ROA covers it. Add a ROA for AS355, maxLength 17.

671 of 673

Route object: none

55.46.0.0/17

No route object for it. Add a route object with origin AS355 in the RIR database for the space.

671 of 673

ROA: none

55.46.128.0/17

No ROA covers it. Add a ROA for AS355, maxLength 17.

671 of 673

Route object: none

55.46.128.0/17

No route object for it. Add a route object with origin AS355 in the RIR database for the space.

671 of 673

ROA: none

2608:18a:5200::/40

No ROA covers it. Add a ROA for AS355, maxLength 40.

636 of 636

Route object: none

2608:18a:5200::/40

No route object for it. Add a route object with origin AS355 in the RIR database for the space.

636 of 636

Route objects not announced

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