bgpreport

Network · data from 2026-11-12

AS131646 CORE WINNER CO.,LIMITED TAIWAN BRANCH

Registry name: COREWINNER-AS-TW - CORE WINNER CO.,LIMITED TAIWAN BRANCH, TW · PeeringDB

12IPv4 routes 100.0% RPKI valid · 83.3% with a route object
0IPv6 routes
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
3Route objects not announced registered with origin AS131646, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131646, 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.
154.3.75.0/24 Valid Nonecovered by 154.3.74.0/23 673 100% 67
154.3.74.0/24 Valid Nonecovered by 154.3.74.0/23 672 100% 67
150.107.60.0/24 Valid Other IRR onlyRADB 673 100% 67
150.107.62.0/24 Valid Other IRR onlyRADB 673 100% 67
43.224.23.0/24 Valid Other IRR onlyRADB 672 100% 67
43.229.155.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
49.128.203.0/24 Valid RIR databaseAPNIC 673 100% 67
103.183.126.0/24 Valid RIR databaseAPNIC 673 100% 67
36.255.192.0/24 Valid RIR databaseAPNIC 672 100% 67
38.126.72.0/24 Valid RIR databaseARIN 672 100% 67
43.252.209.0/24 Valid RIR databaseAPNIC 672 100% 67
103.225.196.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS131646's PeeringDB record names no 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: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none154.3.75.0/24No route object for it. A route object for 154.3.74.0/23 with origin AS131646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131646 in the RIR database for the space.673 of 673
Route object: none154.3.74.0/24No route object for it. A route object for 154.3.74.0/23 with origin AS131646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131646 in the RIR database for the space.672 of 673
Route object: RIR150.107.60.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR150.107.62.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.224.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.161.78.0/23APNICNo ROA
154.3.74.0/23ARINValid
2001:470:1a1::/48ARINValid

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.