Network · data from 2026-11-12
AS18045 SINOPAC - SinoPac Holdings Corporate Network
Registry name: SINOPAC - SinoPac Holdings Corporate Network, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18045, 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.
| 211.76.144.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.146.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.147.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.148.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.150.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.151.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.155.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.156.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.158.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.159.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.76.152.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 211.76.157.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS18045 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 16 are in fix.csv.
- Route object: RIR12
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 211.76.144.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.146.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.147.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.148.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.150.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.151.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.155.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.156.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.158.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.159.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.152.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.76.157.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18045 whose prefix no peer sees AS18045 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 211.76.144.0/20 | NTTCOM, RADB | Valid |
| 211.76.145.0/24 | NTTCOM, RADB | Valid |
| 211.76.149.0/24 | RADB | Valid |
| 211.76.153.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.