bgpreport

Network · data from 2026-11-12

AS17516 NTTCOMWARE

Registry name: NTTCOMWARE - NTT COMWARE CORPORATION, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17516, 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.222.121.0/24 No ROA Other IRR onlyRADB 673 100% 67
132.222.160.0/24 No ROA Other IRR onlyRADB 673 100% 67
132.222.192.0/24 No ROA Other IRR onlyRADB 673 100% 67
132.222.193.0/24 No ROA Other IRR onlyRADB 673 100% 67
132.222.224.0/24 No ROA Other IRR onlyRADB 673 100% 67
163.137.128.0/19 No ROA Other IRR onlyRADB 672 100% 67
163.137.188.0/24 No ROA Other IRR onlyRADB 672 100% 67
163.137.194.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.196.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.200.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.202.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.204.0/22 No ROA Other IRR onlyRADB 672 100% 67
163.137.208.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.212.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.214.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.216.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.218.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.220.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.224.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.226.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.230.0/23 No ROA Other IRR onlyRADB 672 100% 67
163.137.232.0/21 No ROA Other IRR onlyRADB 672 100% 67
2403:2d00:3::/48 No ROA Other IRR onlyRADB 635 100% 68
2403:2d00:8000::/33 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS17516's PeeringDB record names no 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 65 are in fix.csv.

  • ROA: none24
  • Route object: RIR24
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none132.222.121.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.673 of 673
Route object: RIR132.222.121.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none132.222.160.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.673 of 673
Route object: RIR132.222.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none132.222.192.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.673 of 673
Route object: RIR132.222.192.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none132.222.193.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.673 of 673
Route object: RIR132.222.193.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none132.222.224.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.673 of 673
Route object: RIR132.222.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none163.137.128.0/19No ROA covers it. Add a ROA for AS17516, maxLength 19.672 of 673
Route object: RIR163.137.128.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.188.0/24No ROA covers it. Add a ROA for AS17516, maxLength 24.672 of 673
Route object: RIR163.137.188.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.194.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.194.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.196.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.196.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.200.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.200.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.202.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.202.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.204.0/22No ROA covers it. Add a ROA for AS17516, maxLength 22.672 of 673
Route object: RIR163.137.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.208.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.208.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.212.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.212.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.214.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.214.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.216.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.216.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.218.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.218.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.220.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.220.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.224.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.224.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.226.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.226.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.230.0/23No ROA covers it. Add a ROA for AS17516, maxLength 23.672 of 673
Route object: RIR163.137.230.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none163.137.232.0/21No ROA covers it. Add a ROA for AS17516, maxLength 21.672 of 673
Route object: RIR163.137.232.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2403:2d00:3::/48No ROA covers it. Add a ROA for AS17516, maxLength 48.635 of 636
Route object: RIR2403:2d00:3::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2403:2d00:8000::/33No ROA covers it. Add a ROA for AS17516, maxLength 33.635 of 636
Route object: RIR2403:2d00:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.6.112.0/22RADBNo ROA
132.222.0.0/16RADBNo ROA
132.222.1.0/24RADBNo ROA
132.222.122.0/24RADBNo ROA
163.137.0.0/16RADBNo ROA
163.137.191.0/24RADBNo ROA
163.137.198.0/24RADBNo ROA
163.137.199.0/24RADBNo ROA
163.137.210.0/24RADBNo ROA
163.137.211.0/24RADBNo ROA
163.137.228.0/24RADBNo ROA
163.137.229.0/24RADBNo ROA
163.137.254.0/24RADBNo ROA
2403:2d00::/32RADBNo ROA
2403:2d00::/33RADBNo ROA
2403:2d00:3:1a::/64RADBNo ROA
2403:2d00:7ffe::/48RADBNo 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.