Network · data from 2026-11-12
AS132883 TOPWAY-AS-AP - TOPWAY GLOBAL LIMITED
Registry name: TOPWAY-AS-AP - TOPWAY GLOBAL LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132883, 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.56.16.112/32 | Invalid: maxLength | Nonecovered by 103.56.16.0/24 | 2 0%low visibility |
| 103.144.240.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 43.246.208.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.246.209.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.246.210.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.246.211.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.108.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.109.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.110.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.111.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 43.251.236.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 43.251.237.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 43.251.238.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 43.251.239.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.43.16.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.43.17.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.43.18.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.43.19.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.16.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.17.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.18.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.56.19.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.83.8.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.83.9.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.83.10.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.83.11.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.115.236.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.115.237.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.115.238.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.115.239.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.87.8.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.87.9.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.87.10.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.87.11.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.147.12.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.147.13.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS132883 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 60 are in fix.csv.
- ROA: maxLength1
- ROA: none9
- Route object: none1
- Route object: RIR21
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.56.16.112/32 | ROA 103.56.16.0/24 AS132883 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.56.16.112/32. |
| Route object: none | 103.56.16.112/32 | No route object for it. A route object for 103.56.16.0/24 with origin AS132883 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS132883 in the RIR database for the space. |
| ROA: none | 103.144.240.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| Route object: RIR | 103.144.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 43.246.208.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 43.246.209.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 43.246.210.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 43.246.211.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 103.27.108.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 103.27.109.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 103.27.110.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| ROA: none | 103.27.111.0/24 | No ROA covers it. Add a ROA for AS132883, maxLength 24. |
| Route object: RIR | 43.251.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.251.237.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.251.238.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.251.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.16.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.17.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.18.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.19.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.16.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.17.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.18.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.19.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.83.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.83.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.83.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.83.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132883 whose prefix no peer sees AS132883 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.229.228.0/24 | NTTCOM, RADB | No ROA |
| 43.229.229.0/24 | NTTCOM, RADB | No ROA |
| 43.229.230.0/24 | NTTCOM, RADB | No ROA |
| 43.229.231.0/24 | NTTCOM, RADB | No ROA |
| 43.246.208.0/22 | RADB | No ROA |
| 45.115.238.0/23 | NTTCOM, RADB | No ROA |
| 103.27.108.0/22 | RADB | No ROA |
| 103.64.12.0/24 | REACH | Invalid: origin |
| 103.144.241.0/24 | APNIC | Valid |
| 103.145.190.0/23 | APNIC | Valid |
| 103.145.190.0/24 | APNIC | Valid |
| 103.145.191.0/24 | APNIC | Valid |
| 103.149.152.0/23 | NTTCOM, RADB | No ROA |
| 103.237.92.0/23 | APNIC | Valid |
| 103.237.92.0/24 | APNIC | Valid |
| 103.237.93.0/24 | APNIC | Valid |
| 103.255.176.0/22 | NTTCOM, RADB | No ROA |
| 103.255.176.0/24 | NTTCOM, RADB | No ROA |
| 103.255.177.0/24 | NTTCOM, RADB | No ROA |
| 103.255.178.0/24 | NTTCOM, RADB | No ROA |
| 103.255.179.0/24 | NTTCOM, RADB | No ROA |
| 116.204.208.0/24 | APNIC, NTTCOM, RADB | Valid |
| 116.204.209.0/24 | APNIC, NTTCOM, RADB | Valid |
| 116.204.210.0/24 | APNIC, NTTCOM, RADB | Valid |
| 194.32.148.0/24 | RADB | Valid |
| 194.32.149.0/24 | RADB | Valid |
| 2402:3320:3320::/48 | APNIC | Valid |
| 2407:a980::/32 | 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.