bgpreport

Network · data from 2026-11-12

AS38341 HCENET - HEXIE Information technology Co., Ltd.

Registry name: HCENET - HEXIE Information technology Co., Ltd., CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38341, 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.
61.236.80.0/20 Valid None 5 1%low visibility 6
61.236.96.0/20 Valid None 5 1%low visibility 6
61.236.112.0/21 Valid None 5 1%low visibility 6
122.72.57.0/24 Valid None 5 1%low visibility 6
211.98.95.0/24 Valid None 5 1%low visibility 6
211.98.176.0/24 Valid None 5 1%low visibility 6
211.98.188.0/23 Valid None 5 1%low visibility 6
122.64.0.0/17 Valid Other IRR onlyNTTCOM, RADB 5 1%low visibility 6
122.64.128.0/17 Valid Other IRR onlyNTTCOM, RADB 5 1%low visibility 6
123.83.128.0/17 Valid Other IRR onlyNTTCOM, RADB 5 1%low visibility 6

AS-SET

AS38341 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 50 are in fix.csv.

  • Route object: none7
  • Route object: RIR3
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
Route object: none61.236.80.0/20No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none61.236.96.0/20No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none61.236.112.0/21No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none122.72.57.0/24No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none211.98.95.0/24No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none211.98.176.0/24No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: none211.98.188.0/23No route object for it. Add a route object with origin AS38341 in the RIR database for the space.5 of 673
Route object: RIR122.64.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR122.64.128.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR123.83.128.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

110.110.176.0/22NTTCOM, RADBNo ROA
110.110.180.0/22NTTCOM, RADBNo ROA
110.110.184.0/22NTTCOM, RADBNo ROA
110.110.188.0/22NTTCOM, RADBNo ROA
110.110.192.0/22NTTCOM, RADBNo ROA
110.110.204.0/22NTTCOM, RADBNo ROA
110.111.28.0/22NTTCOM, RADBNo ROA
110.111.148.0/22NTTCOM, RADBNo ROA
110.111.224.0/22NTTCOM, RADBNo ROA
110.111.228.0/22NTTCOM, RADBNo ROA
110.111.232.0/22NTTCOM, RADBNo ROA
110.111.236.0/22NTTCOM, RADBNo ROA
111.137.0.0/16NTTCOM, RADBNo ROA
122.65.0.0/17NTTCOM, RADBNo ROA
122.65.0.0/19NTTCOM, RADBNo ROA
122.65.0.0/21NTTCOM, RADBNo ROA
122.65.32.0/19NTTCOM, RADBNo ROA
122.65.32.0/20NTTCOM, RADBNo ROA
122.65.32.0/22NTTCOM, RADBNo ROA
122.65.36.0/22NTTCOM, RADBNo ROA
122.65.40.0/22NTTCOM, RADBNo ROA
122.65.44.0/22NTTCOM, RADBNo ROA
122.65.128.0/17NTTCOM, RADBNo ROA
122.65.132.0/22NTTCOM, RADBNo ROA
122.65.136.0/22NTTCOM, RADBNo ROA
122.65.140.0/22NTTCOM, RADBNo ROA
122.72.21.0/24NTTCOM, RADBNo ROA
122.72.56.0/24NTTCOM, RADBNo ROA
123.83.0.0/17NTTCOM, RADBNo ROA
123.83.0.0/18NTTCOM, RADBNo ROA
222.32.0.0/20NTTCOM, RADBNo ROA
222.32.16.0/21NTTCOM, RADBNo ROA
222.32.104.0/22NTTCOM, RADBNo ROA
222.32.136.0/22NTTCOM, RADBNo ROA
222.32.140.0/22NTTCOM, RADBNo ROA
222.32.168.0/21NTTCOM, RADBNo ROA
222.56.128.0/18NTTCOM, RADBNo ROA
222.56.192.0/18NTTCOM, RADBNo ROA
222.57.248.0/22NTTCOM, RADBNo ROA
222.57.252.0/22NTTCOM, RADBNo 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.