Network · data from 2026-11-12
AS17962 Topway-Net - ShenZhen Topway Video Communication Co. Ltd
Registry name: Topway-Net - ShenZhen Topway Video Communication Co. Ltd, CN · not in PeeringDB
30IPv4 routes
100.0% RPKI valid · 73.3% with a route object
6IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS17962, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17962, 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.12.184.0/22 | Valid | None | 673 100% |
| 116.76.128.0/17 | Valid | Nonecovered by 116.76.0.0/15 | 673 100% |
| 116.77.0.0/17 | Valid | Nonecovered by 116.76.0.0/15 | 673 100% |
| 180.200.252.0/22 | Valid | None | 673 100% |
| 222.248.0.0/18 | Valid | Nonecovered by 222.248.0.0/17 | 673 100% |
| 219.234.112.0/20 | Valid | Nonecovered by 219.234.96.0/19 | 672 100% |
| 116.77.37.0/24 | Valid | Nonecovered by 116.76.0.0/15 | 671 100% |
| 2400:ee00:ffec::/48 | Valid | None | 636 100% |
| 2400:ee00:ffed::/48 | Valid | None | 636 100% |
| 2400:ee00:ffee::/48 | Valid | None | 636 100% |
| 2400:ee00:ffef::/48 | Valid | None | 636 100% |
| 2400:ee00:fff0::/44 | Valid | None | 636 100% |
| 2400:ee00::/32 | Valid | None | 43 7%low visibility |
| 219.232.187.0/24 | Valid | Nonecovered by 219.232.160.0/19 | 2 0%low visibility |
| 111.221.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 111.222.0.0/16 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.44.0.0/15 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.44.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.44.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.45.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.45.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.76.0.0/15 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 116.76.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.77.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.88.32.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.148.192.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 219.232.160.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 219.234.96.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 222.125.0.0/16 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 222.125.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 222.125.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 222.248.0.0/16 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 222.248.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 36.36.0.0/16 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 223.212.0.0/15 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 222.248.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS17962 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 45 are in fix.csv.
- Route object: none14
- Route object: RIR22
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.12.184.0/22 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 116.76.128.0/17 | No route object for it. A route object for 116.76.0.0/15 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 116.77.0.0/17 | No route object for it. A route object for 116.76.0.0/15 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 180.200.252.0/22 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 222.248.0.0/18 | No route object for it. A route object for 222.248.0.0/17 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 219.234.112.0/20 | No route object for it. A route object for 219.234.96.0/19 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 116.77.37.0/24 | No route object for it. A route object for 116.76.0.0/15 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00:ffec::/48 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00:ffed::/48 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00:ffee::/48 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00:ffef::/48 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00:fff0::/44 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 2400:ee00::/32 | No route object for it. Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: none | 219.232.187.0/24 | No route object for it. A route object for 219.232.160.0/19 with origin AS17962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17962 in the RIR database for the space. |
| Route object: RIR | 111.221.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.222.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.44.0.0/15 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.44.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.44.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.45.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.45.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.76.0.0/15 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 116.76.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.77.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.88.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.148.192.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.232.160.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.234.96.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.125.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.125.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.125.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.248.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.248.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 36.36.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.212.0.0/15 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.248.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17962 whose prefix no peer sees AS17962 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 111.221.128.0/20 | NTTCOM, RADB | Valid |
| 111.221.144.0/20 | NTTCOM, RADB | Valid |
| 111.221.160.0/20 | NTTCOM, RADB | Valid |
| 111.221.176.0/20 | NTTCOM, RADB | Valid |
| 111.221.192.0/20 | NTTCOM, RADB | Valid |
| 111.221.208.0/20 | NTTCOM, RADB | Valid |
| 111.221.224.0/20 | NTTCOM, RADB | Valid |
| 111.221.240.0/20 | NTTCOM, RADB | Valid |
| 116.205.128.0/17 | NTTCOM, RADB | No ROA |
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.