bgpreport

Network · data from 2026-11-12

AS140595 YCHKL-AS-AP - YunJie Communication HK Company Limited

Registry name: YCHKL-AS-AP - YunJie Communication HK Company Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140595, 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.
102.164.56.0/24 No ROA Other IRR onlyRADB 672 100% 67
102.164.57.0/24 No ROA Other IRR onlyRADB 672 100% 67
102.164.58.0/24 No ROA Other IRR onlyRADB 672 100% 67
102.164.59.0/24 No ROA Other IRR onlyRADB 672 100% 67
102.164.56.0/22 No ROA Other IRR onlyRADB 671 100% 67
216.116.170.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
216.116.169.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
154.92.105.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.249.82.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.249.96.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.249.101.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.249.115.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
154.92.104.0/22 Valid RIR databaseAFRINIC, RADB 670 100% 67

AS-SET

AS140595 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 12 are in fix.csv.

  • ROA: none5
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none102.164.56.0/24No ROA covers it. Add a ROA for AS140595, maxLength 24.672 of 673
Route object: RIR102.164.56.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.164.57.0/24No ROA covers it. Add a ROA for AS140595, maxLength 24.672 of 673
Route object: RIR102.164.57.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.164.58.0/24No ROA covers it. Add a ROA for AS140595, maxLength 24.672 of 673
Route object: RIR102.164.58.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.164.59.0/24No ROA covers it. Add a ROA for AS140595, maxLength 24.672 of 673
Route object: RIR102.164.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.164.56.0/22No ROA covers it. Add a ROA for AS140595, maxLength 22.671 of 673
Route object: RIR102.164.56.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.116.170.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR216.116.169.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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