Network · data from 2026-11-12
AS131679 COREWINNER-AS-TW - CORE WINNER CO.,LIMITED TAIWAN BRANCH
Registry name: COREWINNER-AS-TW - CORE WINNER CO.,LIMITED TAIWAN BRANCH, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131679, 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.
| 150.116.80.0/24 | Valid | Other IRR onlyRADB | 193 29% |
| 103.117.106.0/24 | Valid | RIR databaseAPNIC, RADB | 292 43% |
| 156.242.9.0/24 | Valid | RIR databaseAFRINIC, RADB | 193 29% |
| 103.68.138.0/24 | Valid | RIR databaseAPNIC, RADB | 192 29% |
AS-SET
AS131679 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 19 are in fix.csv.
- Route object: RIR1
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 150.116.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131679 whose prefix no peer sees AS131679 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.150.230.0/23 | RADB | No ROA |
| 103.150.230.0/24 | RADB | No ROA |
| 103.166.81.0/24 | APNIC | Valid |
| 154.19.176.0/21 | RADB | No ROA |
| 154.19.176.0/22 | RADB | No ROA |
| 154.19.176.0/23 | RADB | No ROA |
| 154.19.176.0/24 | RADB | No ROA |
| 154.19.177.0/24 | RADB | No ROA |
| 154.19.178.0/23 | RADB | No ROA |
| 154.19.178.0/24 | RADB | No ROA |
| 154.19.179.0/24 | RADB | No ROA |
| 154.19.180.0/22 | RADB | No ROA |
| 154.19.180.0/23 | RADB | No ROA |
| 154.19.180.0/24 | RADB | No ROA |
| 154.19.181.0/24 | RADB | No ROA |
| 154.19.182.0/23 | RADB | No ROA |
| 154.19.182.0/24 | RADB | No ROA |
| 154.19.183.0/24 | RADB | No 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.