bgpreport

Network · data from 2026-11-12

AS63718 HZ-YOUYUN - Hangzhou YouYun Technology Co., Ltd.

Registry name: HZ-YOUYUN - Hangzhou YouYun Technology Co., Ltd., CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63718, 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.
103.105.220.0/23 Valid Nonecovered by 103.105.220.0/22 671 100% 67
103.105.222.0/23 Valid Nonecovered by 103.105.220.0/22 671 100% 67
103.105.220.0/22 Valid Other IRR onlyRADB 673 100% 67
180.178.232.0/22 Valid Other IRR onlyRADB 667 99% 67
180.178.208.0/20 Valid Other IRR onlyRADB 665 99% 67
180.178.224.0/21 Valid Other IRR onlyRADB 665 99% 67
180.178.248.0/22 Valid Other IRR onlyRADB 665 99% 67
2401:d920::/48 Valid Other IRR onlyRADB 629 99% 67

AS-SET

AS63718 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 8 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none103.105.220.0/23No route object for it. A route object for 103.105.220.0/22 with origin AS63718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63718 in the RIR database for the space.671 of 673
Route object: none103.105.222.0/23No route object for it. A route object for 103.105.220.0/22 with origin AS63718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63718 in the RIR database for the space.671 of 673
Route object: RIR103.105.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.178.232.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR180.178.208.0/20Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR180.178.224.0/21Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR180.178.248.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2401:d920::/48Route object only in RADB. Add it in the RIR database for the space.629 of 636

Route objects not announced

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