bgpreport

Network · data from 2026-11-12

AS1733 DISACENT-NIPR-ASN - United States Department of Defense (DoD)

Registry name: DISACENT-NIPR-ASN - United States Department of Defense (DoD), US · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 10.0% with a route object
3IPv6 routes 0.0% RPKI valid · 0.0% with a route object
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
1Route objects not announced registered with origin AS1733, seen from no peer

Announced routes

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

134.229.70.0/24 No ROA None 672 100% 67
139.242.216.0/24 No ROA None 672 100% 67
209.22.82.0/24 No ROA None 672 100% 67
214.48.52.0/22 No ROA None 671 100% 67
214.48.60.0/22 No ROA None 671 100% 67
214.72.7.0/24 No ROA None 671 100% 67
214.72.17.0/24 No ROA None 671 100% 67
215.1.42.0/23 No ROA None 671 100% 67
215.65.50.0/23 No ROA None 671 100% 67
2608:8105:1::/48 No ROA None 636 100% 67
2608:8105:a119::/48 No ROA None 636 100% 67
2608:8106:b83::/48 No ROA None 636 100% 67
134.229.68.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67

AS-SET

AS1733 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 27 are in fix.csv.

  • ROA: none13
  • Route object: none12
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none134.229.70.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.672 of 673
Route object: none134.229.70.0/24No route object for it. Add a route object with origin AS1733 in the RIR database for the space.672 of 673
ROA: none139.242.216.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.672 of 673
Route object: none139.242.216.0/24No route object for it. Add a route object with origin AS1733 in the RIR database for the space.672 of 673
ROA: none209.22.82.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.672 of 673
Route object: none209.22.82.0/24No route object for it. Add a route object with origin AS1733 in the RIR database for the space.672 of 673
ROA: none214.48.52.0/22No ROA covers it. Add a ROA for AS1733, maxLength 22.671 of 673
Route object: none214.48.52.0/22No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none214.48.60.0/22No ROA covers it. Add a ROA for AS1733, maxLength 22.671 of 673
Route object: none214.48.60.0/22No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none214.72.7.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.671 of 673
Route object: none214.72.7.0/24No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none214.72.17.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.671 of 673
Route object: none214.72.17.0/24No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none215.1.42.0/23No ROA covers it. Add a ROA for AS1733, maxLength 23.671 of 673
Route object: none215.1.42.0/23No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none215.65.50.0/23No ROA covers it. Add a ROA for AS1733, maxLength 23.671 of 673
Route object: none215.65.50.0/23No route object for it. Add a route object with origin AS1733 in the RIR database for the space.671 of 673
ROA: none2608:8105:1::/48No ROA covers it. Add a ROA for AS1733, maxLength 48.636 of 636
Route object: none2608:8105:1::/48No route object for it. Add a route object with origin AS1733 in the RIR database for the space.636 of 636
ROA: none2608:8105:a119::/48No ROA covers it. Add a ROA for AS1733, maxLength 48.636 of 636
Route object: none2608:8105:a119::/48No route object for it. Add a route object with origin AS1733 in the RIR database for the space.636 of 636
ROA: none2608:8106:b83::/48No ROA covers it. Add a ROA for AS1733, maxLength 48.636 of 636
Route object: none2608:8106:b83::/48No route object for it. Add a route object with origin AS1733 in the RIR database for the space.636 of 636
ROA: none134.229.68.0/24No ROA covers it. Add a ROA for AS1733, maxLength 24.672 of 673
Route object: RIR134.229.68.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

138.160.240.0/24NTTCOMNo 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.