Network · data from 2026-11-12

AS409 AFCONC-BLOCK1-AS - Air Force Systems Networking

Registry name: AFCONC-BLOCK1-AS - Air Force Systems Networking, US · not in PeeringDB

13IPv4 routes 0.0% RPKI valid · 7.7% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

13No ROA 12 with no route object for this origin

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

5Route objects not announced registered with origin AS409, seen from no peer

Announced routes

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


131.36.0.0/16	No ROA	None	672 100%	67
131.36.116.0/24	No ROA	None	672 100%	67
131.47.0.0/16	No ROA	None	672 100%	67
131.47.100.0/24	No ROA	None	672 100%	67
131.47.106.0/24	No ROA	None	672 100%	67
132.3.8.0/22	No ROA	None	672 100%	67
132.15.0.0/16	No ROA	None	672 100%	67
132.15.225.0/24	No ROA	None	672 100%	67
132.20.0.0/16	No ROA	None	672 100%	67
132.20.251.0/24	No ROA	None	672 100%	67
143.140.64.0/21	No ROA	None	672 100%	67
143.140.70.0/24	No ROA	None	672 100%	67
128.216.0.0/20	No ROA	Other IRR onlyNTTCOM	672 100%	67

AS-SET

AS409 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 31 are in fix.csv.

ROA: none13
Route object: none12
Route object: RIR1
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
ROA: none	131.36.0.0/16	No ROA covers it. Add a ROA for AS409, maxLength 16.	672 of 673
Route object: none	131.36.0.0/16	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	131.36.116.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	131.36.116.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	131.47.0.0/16	No ROA covers it. Add a ROA for AS409, maxLength 16.	672 of 673
Route object: none	131.47.0.0/16	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	131.47.100.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	131.47.100.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	131.47.106.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	131.47.106.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	132.3.8.0/22	No ROA covers it. Add a ROA for AS409, maxLength 22.	672 of 673
Route object: none	132.3.8.0/22	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	132.15.0.0/16	No ROA covers it. Add a ROA for AS409, maxLength 16.	672 of 673
Route object: none	132.15.0.0/16	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	132.15.225.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	132.15.225.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	132.20.0.0/16	No ROA covers it. Add a ROA for AS409, maxLength 16.	672 of 673
Route object: none	132.20.0.0/16	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	132.20.251.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	132.20.251.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	143.140.64.0/21	No ROA covers it. Add a ROA for AS409, maxLength 21.	672 of 673
Route object: none	143.140.64.0/21	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	143.140.70.0/24	No ROA covers it. Add a ROA for AS409, maxLength 24.	672 of 673
Route object: none	143.140.70.0/24	No route object for it. Add a route object with origin AS409 in the RIR database for the space.	672 of 673
ROA: none	128.216.0.0/20	No ROA covers it. Add a ROA for AS409, maxLength 20.	672 of 673
Route object: RIR	128.216.0.0/20	Route object only in NTTCOM. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

131.36.0.0/16

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

672 of 673

Route object: none

131.36.0.0/16

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

672 of 673

ROA: none

131.36.116.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

131.36.116.0/24

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

672 of 673

ROA: none

131.47.0.0/16

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

672 of 673

Route object: none

131.47.0.0/16

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

672 of 673

ROA: none

131.47.100.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

131.47.100.0/24

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

672 of 673

ROA: none

131.47.106.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

131.47.106.0/24

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

672 of 673

ROA: none

132.3.8.0/22

No ROA covers it. Add a ROA for AS409, maxLength 22.

672 of 673

Route object: none

132.3.8.0/22

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

672 of 673

ROA: none

132.15.0.0/16

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

672 of 673

Route object: none

132.15.0.0/16

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

672 of 673

ROA: none

132.15.225.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

132.15.225.0/24

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

672 of 673

ROA: none

132.20.0.0/16

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

672 of 673

Route object: none

132.20.0.0/16

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

672 of 673

ROA: none

132.20.251.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

132.20.251.0/24

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

672 of 673

ROA: none

143.140.64.0/21

No ROA covers it. Add a ROA for AS409, maxLength 21.

672 of 673

Route object: none

143.140.64.0/21

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

672 of 673

ROA: none

143.140.70.0/24

No ROA covers it. Add a ROA for AS409, maxLength 24.

672 of 673

Route object: none

143.140.70.0/24

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

672 of 673

ROA: none

128.216.0.0/20

No ROA covers it. Add a ROA for AS409, maxLength 20.

672 of 673

Route object: RIR

128.216.0.0/20

Route object only in NTTCOM. Add it in the RIR database for the space.

672 of 673

Route objects not announced

Route objects with origin AS409 whose prefix no peer sees AS409 announce. Many are kept on purpose (backup routes, space announced only in some places).


128.26.35.0/24	NTTCOM	No ROA
128.26.36.0/24	NTTCOM	No ROA
128.26.37.0/24	NTTCOM	No ROA
128.26.38.0/24	NTTCOM	No ROA
128.26.39.0/24	NTTCOM	No ROA

128.26.35.0/24

NTTCOM

No ROA

128.26.36.0/24

NTTCOM

No ROA

128.26.37.0/24

NTTCOM

No ROA

128.26.38.0/24

NTTCOM

No ROA

128.26.39.0/24

NTTCOM

No ROA

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.