bgpreport

Network · data from 2026-11-12

AS427 AFCONC-BLOCK1-AS - Air Force Systems Networking

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS427, 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.
132.3.12.0/22 No ROA None 672 100% 67
132.16.0.0/16 No ROA Other origin only 672 100% 67
132.61.0.0/16 No ROA Other origin only 672 100% 67
132.61.176.0/24 No ROA None 672 100% 67
192.77.104.0/24 No ROA Other origin only 672 100% 67
198.218.204.0/24 No ROA Other origin only 672 100% 67
199.251.88.0/23 No ROA None 672 100% 67

AS-SET

AS427 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: none132.3.12.0/22No ROA covers it. Add a ROA for AS427, maxLength 22.672 of 673
Route object: none132.3.12.0/22No route object for it. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none132.16.0.0/16No ROA covers it. Add a ROA for AS427, maxLength 16.672 of 673
Route object: none132.16.0.0/16Route objects for it name AS400. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none132.61.0.0/16No ROA covers it. Add a ROA for AS427, maxLength 16.672 of 673
Route object: none132.61.0.0/16Route objects for it name AS400. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none132.61.176.0/24No ROA covers it. Add a ROA for AS427, maxLength 24.672 of 673
Route object: none132.61.176.0/24No route object for it. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none192.77.104.0/24No ROA covers it. Add a ROA for AS427, maxLength 24.672 of 673
Route object: none192.77.104.0/24Route objects for it name AS400. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none198.218.204.0/24No ROA covers it. Add a ROA for AS427, maxLength 24.672 of 673
Route object: none198.218.204.0/24Route objects for it name AS400. Add a route object with origin AS427 in the RIR database for the space.672 of 673
ROA: none199.251.88.0/23No ROA covers it. Add a ROA for AS427, maxLength 23.672 of 673
Route object: none199.251.88.0/23No route object for it. Add a route object with origin AS427 in the RIR database for the space.672 of 673

Route objects not announced

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