Network · data from 2026-11-12
AS17710 PIINET-TW - President Information Corp.
Registry name: PIINET-TW - President Information Corp., TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17710, 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.
| 103.234.80.0/24 | Valid | Nonecovered by 103.234.80.0/22 | 673 100% |
| 103.234.81.0/24 | Valid | Nonecovered by 103.234.80.0/22 | 673 100% |
| 103.234.82.0/24 | Valid | Nonecovered by 103.234.80.0/22 | 673 100% |
| 103.234.83.0/24 | Valid | Nonecovered by 103.234.80.0/22 | 673 100% |
| 150.107.64.0/24 | Valid | Nonecovered by 150.107.64.0/22 | 673 100% |
| 61.57.224.0/20 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.224.0/21 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.226.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.228.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.233.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.239.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.234.80.0/22 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 150.107.64.0/22 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 61.57.238.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS17710 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 38 are in fix.csv.
- Route object: none5
- Route object: RIR9
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.234.80.0/24 | No route object for it. A route object for 103.234.80.0/22 with origin AS17710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17710 in the RIR database for the space. |
| Route object: none | 103.234.81.0/24 | No route object for it. A route object for 103.234.80.0/22 with origin AS17710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17710 in the RIR database for the space. |
| Route object: none | 103.234.82.0/24 | No route object for it. A route object for 103.234.80.0/22 with origin AS17710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17710 in the RIR database for the space. |
| Route object: none | 103.234.83.0/24 | No route object for it. A route object for 103.234.80.0/22 with origin AS17710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17710 in the RIR database for the space. |
| Route object: none | 150.107.64.0/24 | No route object for it. A route object for 150.107.64.0/22 with origin AS17710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17710 in the RIR database for the space. |
| Route object: RIR | 61.57.224.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.224.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.226.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.228.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.233.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.239.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.234.80.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 150.107.64.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.238.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17710 whose prefix no peer sees AS17710 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.57.224.0/22 | NTTCOM | Valid |
| 61.57.224.0/23 | NTTCOM | Valid |
| 61.57.224.0/24 | NTTCOM | Valid |
| 61.57.225.0/24 | NTTCOM | Valid |
| 61.57.226.0/23 | NTTCOM | Valid |
| 61.57.227.0/24 | NTTCOM | Valid |
| 61.57.228.0/22 | NTTCOM | Valid |
| 61.57.228.0/23 | NTTCOM | Valid |
| 61.57.229.0/24 | NTTCOM | Valid |
| 61.57.230.0/23 | NTTCOM | Valid |
| 61.57.230.0/24 | NTTCOM | Valid |
| 61.57.231.0/24 | NTTCOM | Valid |
| 61.57.232.0/21 | NTTCOM | Valid |
| 61.57.232.0/22 | NTTCOM | Valid |
| 61.57.232.0/23 | NTTCOM | Valid |
| 61.57.232.0/24 | NTTCOM | Valid |
| 61.57.234.0/23 | NTTCOM | Valid |
| 61.57.234.0/24 | NTTCOM | Valid |
| 61.57.235.0/24 | NTTCOM | Valid |
| 61.57.236.0/22 | NTTCOM | Valid |
| 61.57.236.0/23 | NTTCOM | Valid |
| 61.57.236.0/24 | NTTCOM | Valid |
| 61.57.237.0/24 | NTTCOM | Valid |
| 61.57.238.0/23 | NTTCOM | 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.