Network · data from 2026-11-12
AS7539 TaiWan Advanced Research and Education Network(TWAREN)
Registry name: TWAREN-TW - National Center for High-performance Computing, TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7539, 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.
| 120.101.64.0/22 | Invalid: origin | None | 2 0%low visibility |
| 203.145.200.48/28 | Invalid: maxLength | Nonecovered by 203.145.200.0/21 | 2 0%low visibility |
| 2001:c58:a000::/35 | Valid | None | 631 99% |
| 103.124.72.0/24 | Valid | Nonecovered by 103.124.72.0/22 | 16 2%low visibility |
| 103.124.73.0/24 | Valid | Nonecovered by 103.124.72.0/22 | 16 2%low visibility |
| 211.73.68.0/23 | Valid | Nonecovered by 211.73.64.0/19 | 16 2%low visibility |
| 211.73.72.0/24 | Valid | Nonecovered by 211.73.64.0/19 | 16 2%low visibility |
| 103.124.74.0/24 | Valid | Nonecovered by 103.124.72.0/22 | 0 0%low visibility |
| 103.124.75.0/24 | Valid | Nonecovered by 103.124.72.0/22 | 0 0%low visibility |
| 140.110.0.0/16 | Valid | RIR databaseAPNIC | 673 100% |
| 140.110.200.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 103.124.72.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 203.145.200.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 203.145.208.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 211.73.64.0/19 | Valid | RIR databaseAPNIC | 672 100% |
| 211.79.48.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 140.110.215.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2001:e10::/32 | Valid | RIR databaseAPNIC, RADB | 632 99% |
| 103.160.220.0/23 | Valid | RIR databaseAPNIC | 20 3%low visibility |
AS-SET
PeeringDB's irr_as_set for AS7539: APNIC::AS7539:AS-TWAREN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS7539 isn't in the set, or no route object for AS7539 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS7539 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS7539:AS-TWAREN | APNIC | 14 | 2 | Yes | 3 |
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 12 are in fix.csv.
- ROA: origin1
- ROA: maxLength1
- Route object: none9
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 120.101.64.0/22 | ROAs covering it name AS1659, not AS7539. If AS7539 should announce it, add a ROA for AS7539. |
| Route object: none | 120.101.64.0/22 | No route object for it. Add a route object with origin AS7539 in the RIR database for the space. |
| ROA: maxLength | 203.145.200.48/28 | ROA 203.145.200.0/21 AS7539 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 203.145.200.48/28. |
| Route object: none | 203.145.200.48/28 | No route object for it. A route object for 203.145.200.0/21 with origin AS7539 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 2001:c58:a000::/35 | No route object for it. Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 103.124.72.0/24 | No route object for it. A route object for 103.124.72.0/22 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 103.124.73.0/24 | No route object for it. A route object for 103.124.72.0/22 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 211.73.68.0/23 | No route object for it. A route object for 211.73.64.0/19 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 211.73.72.0/24 | No route object for it. A route object for 211.73.64.0/19 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 103.124.74.0/24 | No route object for it. A route object for 103.124.72.0/22 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
| Route object: none | 103.124.75.0/24 | No route object for it. A route object for 103.124.72.0/22 with origin AS7539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7539 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7539 whose prefix no peer sees AS7539 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:4500:1000::/40 | APNIC | 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.