Network · data from 2026-11-12
AS23675 TSMCGDN-AS-AP - Taiwan Semiconductor Manufactoring Company, Ltd.
Registry name: TSMCGDN-AS-AP - Taiwan Semiconductor Manufactoring Company, Ltd., TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23675, 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.
| 202.126.64.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.65.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.66.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.67.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.68.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.69.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.70.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.71.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.72.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.73.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.74.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.126.75.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.66.100.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.66.101.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.66.102.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.66.245.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 220.128.55.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 106.105.110.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 208.70.204.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS23675 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 37 are in fix.csv.
- Route object: RIR18
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.126.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.70.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.73.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.126.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.66.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.66.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.66.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.66.245.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 220.128.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.105.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23675 whose prefix no peer sees AS23675 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.126.64.0/20 | RADB | Valid |
| 202.126.64.0/21 | RADB | Valid |
| 202.126.64.0/22 | RADB | Valid |
| 202.126.64.0/23 | RADB | Valid |
| 202.126.66.0/23 | RADB | Valid |
| 202.126.68.0/22 | RADB | Valid |
| 202.126.68.0/23 | RADB | Valid |
| 202.126.70.0/23 | RADB | Valid |
| 202.126.72.0/21 | RADB | Valid |
| 202.126.72.0/22 | RADB | Valid |
| 202.126.72.0/23 | RADB | Valid |
| 202.126.74.0/23 | RADB | Valid |
| 202.126.76.0/22 | RADB | Valid |
| 202.126.76.0/23 | RADB | Valid |
| 202.126.76.0/24 | RADB | Valid |
| 202.126.77.0/24 | RADB | Valid |
| 202.126.78.0/23 | RADB | Valid |
| 202.126.78.0/24 | RADB | Valid |
| 202.126.79.0/24 | RADB | Valid |
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.