bgpreport

Network · data from 2026-11-12

AS136970 YISUCLOUDLTD-AS-AP - YISU CLOUD LTD

Registry name: YISUCLOUDLTD-AS-AP - YISU CLOUD LTD, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136970, 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.107.236.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 68
103.107.237.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 68
103.107.238.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 68
154.92.20.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
103.100.61.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
103.100.63.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
154.197.2.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.197.3.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.197.4.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.197.5.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.197.6.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
154.197.7.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 68
156.236.64.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 68
156.236.65.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 68
156.236.67.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 68
156.236.68.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 68
156.236.69.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 68

AS-SET

AS136970 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 22 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none103.107.236.0/24No ROA covers it. Add a ROA for AS136970, maxLength 24.671 of 673
Route object: RIR103.107.236.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.107.237.0/24No ROA covers it. Add a ROA for AS136970, maxLength 24.671 of 673
Route object: RIR103.107.237.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.107.238.0/24No ROA covers it. Add a ROA for AS136970, maxLength 24.671 of 673
Route object: RIR103.107.238.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

39.109.112.0/22APNICNo ROA
39.109.112.0/23APNICNo ROA
39.109.114.0/23APNICNo ROA
39.109.116.0/23APNICNo ROA
39.109.116.0/24APNICNo ROA
39.109.122.0/23APNICNo ROA
103.100.208.0/22APNICNo ROA
103.100.208.0/23APNICNo ROA
103.100.210.0/23APNICNo ROA
103.144.242.0/24RADBNo ROA
103.144.243.0/24RADBNo ROA
103.146.158.0/23APNICValid
103.146.158.0/24APNICValid
154.92.18.0/24AFRINICInvalid: origin
154.209.6.0/23RADBNo ROA
154.221.32.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.