bgpreport

Network · data from 2026-11-12

AS38797 CNLINK-TW-AS-AP - Internet Service Provider. Taiwan

Registry name: CNLINK-TW-AS-AP - Internet Service Provider. Taiwan, TW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38797, 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.
125.62.228.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.230.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.231.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.232.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.233.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.234.0/24 Valid Other IRR onlyREACH 673 100% 68
125.62.227.0/24 Valid Other IRR onlyREACH 672 100% 67
125.62.229.0/24 Valid Other IRR onlyREACH 672 100% 67
125.62.224.0/24 Valid Other IRR onlyREACH 670 100% 66
125.62.225.0/24 Valid Other IRR onlyREACH 670 100% 66
125.62.226.0/24 Valid Other IRR onlyREACH 670 100% 66
125.62.235.0/24 Valid Other IRR onlyREACH 670 100% 66
125.62.236.0/24 Valid Other IRR onlyREACH 670 100% 66
125.62.239.0/24 Valid Other IRR onlyREACH 670 100% 66

AS-SET

AS38797 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 80 are in fix.csv.

  • Route object: RIR14
  • Route object: not announced66
ChangePrefix or setDetailFull-table peers
Route object: RIR125.62.228.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.230.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.231.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.232.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.233.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.234.0/24Route object only in REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR125.62.227.0/24Route object only in REACH. Add it in the RIR database for the space.672 of 673
Route object: RIR125.62.229.0/24Route object only in REACH. Add it in the RIR database for the space.672 of 673
Route object: RIR125.62.224.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR125.62.225.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR125.62.226.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR125.62.235.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR125.62.236.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673
Route object: RIR125.62.239.0/24Route object only in REACH. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

49.246.226.0/24REACHNo ROA
49.246.227.0/24REACHNo ROA
49.246.228.0/24REACHNo ROA
49.246.229.0/24REACHNo ROA
49.246.230.0/24REACHNo ROA
49.246.231.0/24REACHNo ROA
49.246.232.0/24REACHNo ROA
49.246.233.0/24REACHNo ROA
49.246.234.0/24REACHNo ROA
49.246.235.0/24REACHNo ROA
101.36.86.0/24REACHInvalid: origin
103.30.132.0/23RADBNo ROA
103.30.132.0/24RADBNo ROA
103.30.133.0/24RADBNo ROA
103.30.134.0/23RADBNo ROA
103.30.134.0/24RADBNo ROA
103.30.135.0/24RADBNo ROA
118.26.33.0/24REACHNo ROA
122.10.200.0/24REACHInvalid: origin
122.10.201.0/24REACHInvalid: origin
122.10.202.0/24REACHInvalid: origin
122.10.203.0/24REACHInvalid: origin
122.10.204.0/24REACHInvalid: origin
123.108.128.0/24REACHNo ROA
123.108.129.0/24REACHNo ROA
123.108.130.0/24REACHNo ROA
123.108.131.0/24REACHNo ROA
123.108.132.0/24REACHNo ROA
123.108.140.0/24REACHNo ROA
125.62.224.0/20REACHValid
125.62.237.0/24RADB, REACHValid
125.62.238.0/24RADB, REACHValid
180.214.238.0/24RADBNo ROA
183.182.0.0/24RADB, REACHNo ROA
183.182.5.0/24RADB, REACHNo ROA
183.182.6.0/24RADB, REACHNo ROA
183.182.15.0/24RADB, REACHNo ROA
183.182.16.0/24RADB, REACHNo ROA
183.182.25.0/24RADB, REACHNo ROA
183.182.26.0/24RADB, REACHNo ROA
183.182.30.0/23RADBNo ROA
183.182.30.0/24REACHNo ROA
183.182.31.0/24REACHNo ROA
202.131.48.0/24REACHNo ROA
202.131.49.0/24REACHNo ROA
202.131.50.0/24REACHNo ROA
202.131.51.0/24REACHNo ROA
202.131.52.0/24REACHNo ROA
202.131.57.0/24RADBNo ROA
202.131.58.0/24RADBNo ROA
202.181.136.0/24REACHInvalid: origin
202.181.141.0/24REACHInvalid: origin
202.181.143.0/24REACHNo ROA
202.181.144.0/22REACHNo ROA
202.181.150.0/24REACHInvalid: origin
202.181.155.0/24REACHInvalid: origin
202.181.188.0/24REACHInvalid: origin
202.181.189.0/24REACHNo ROA
202.181.218.0/24REACHInvalid: origin
203.70.132.0/22REACHInvalid: origin
203.161.176.0/23REACHNo ROA
203.201.32.0/20REACHInvalid: origin
211.155.64.0/23RADBNo ROA
211.155.64.0/24RADBNo ROA
211.155.66.0/24REACHNo ROA
211.155.79.0/24REACHNo 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.