bgpreport

Network · data from 2026-11-12

AS32720 CANON-ASN - Canon USA Inc.

Registry name: CANON-ASN - Canon USA Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32720, 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.
146.184.120.0/24 No ROA Other origin onlycovered by 146.184.0.0/16 673 100% 67
146.184.121.0/24 No ROA Other origin onlycovered by 146.184.0.0/16 673 100% 67
146.184.0.0/24 No ROA Other IRR onlyRADB 673 100% 67
146.184.6.0/24 No ROA Other IRR onlyRADB 673 100% 67
146.184.122.0/24 No ROA Other IRR onlyRADB 673 100% 67
146.184.123.0/24 No ROA Other IRR onlyRADB 673 100% 67
146.184.152.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
146.184.155.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
146.184.156.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
146.184.157.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
146.184.160.0/20 No ROA Other IRR onlyRADB 673 100% 67
146.184.175.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS32720 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 35 are in fix.csv.

  • ROA: none12
  • Route object: none2
  • Route object: RIR10
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none146.184.120.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: none146.184.120.0/24Route objects for it name AS812, AS26788. A route object for 146.184.0.0/16 with origin AS32720 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32720 in the RIR database for the space.673 of 673
ROA: none146.184.121.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: none146.184.121.0/24Route objects for it name AS812, AS26788. A route object for 146.184.0.0/16 with origin AS32720 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32720 in the RIR database for the space.673 of 673
ROA: none146.184.0.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.6.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.6.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.122.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.122.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.123.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.123.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.152.0/22No ROA covers it. Add a ROA for AS32720, maxLength 22.673 of 673
Route object: RIR146.184.152.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.155.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.155.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.156.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.156.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.157.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.157.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none146.184.160.0/20No ROA covers it. Add a ROA for AS32720, maxLength 20.673 of 673
Route object: RIR146.184.160.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.184.175.0/24No ROA covers it. Add a ROA for AS32720, maxLength 24.673 of 673
Route object: RIR146.184.175.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

146.184.0.0/16RADBNo ROA
146.184.160.0/24RADBNo ROA
146.184.161.0/24RADBNo ROA
146.184.162.0/24RADBNo ROA
146.184.163.0/24RADBNo ROA
146.184.164.0/24RADBNo ROA
146.184.165.0/24RADBNo ROA
146.184.166.0/24RADBNo ROA
146.184.167.0/24RADBNo ROA
146.187.7.0/24RADBNo ROA
146.187.194.0/24RADBNo 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.