Network · data from 2026-11-12
AS7641 CHINABTN - China Broadcasting TV Net
Registry name: CHINABTN - China Broadcasting TV Net, CN · not in PeeringDB
28IPv4 routes
100.0% RPKI valid · 39.3% with a route object
5IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
17 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
38Route objects not announced
registered with origin AS7641, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS7641, 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.89.230.0/23 | Valid | Nonecovered by 211.89.0.0/16 | 671 100% |
| 211.146.0.0/19 | Valid | Nonecovered by 211.146.0.0/16 | 671 100% |
| 211.146.32.0/21 | Valid | Nonecovered by 211.146.0.0/16 | 671 100% |
| 211.89.230.0/24 | Valid | Nonecovered by 211.89.0.0/16 | 84 12% |
| 211.146.5.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.6.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.7.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.10.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.24.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.25.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.34.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.35.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.36.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.37.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.146.38.0/24 | Valid | Nonecovered by 211.146.0.0/16 | 84 12% |
| 211.156.128.0/20 | Valid | Nonecovered by 211.156.128.0/19 | 84 12% |
| 211.156.144.0/20 | Valid | Nonecovered by 211.156.128.0/19 | 84 12% |
| 211.146.20.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 211.156.128.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 2403:600::/32 | Valid | Other IRR onlyNTTCOM, RADB | 636 100% |
| 211.146.21.0/24 | Valid | Other IRR onlyRADB | 104 15% |
| 211.146.22.0/24 | Valid | Other IRR onlyRADB | 104 15% |
| 211.146.23.0/24 | Valid | Other IRR onlyRADB | 104 15% |
| 211.146.1.0/24 | Valid | Other IRR onlyRADB | 84 12% |
| 211.146.8.0/24 | Valid | Other IRR onlyRADB | 84 12% |
| 211.146.12.0/22 | Valid | Other IRR onlyRADB | 84 12% |
| 211.146.26.0/24 | Valid | Other IRR onlyRADB | 84 12% |
| 211.146.32.0/24 | Valid | Other IRR onlyRADB | 84 12% |
| 211.146.33.0/24 | Valid | Other IRR onlyRADB | 84 12% |
| 2403:600:a000::/38 | Valid | Other IRR onlyRADB | 69 11% |
| 2403:600:a600::/48 | Valid | Other IRR onlyRADB | 69 11% |
| 2403:600:a601::/48 | Valid | Other IRR onlyRADB | 69 11% |
| 2403:600:a602::/48 | Valid | Other IRR onlyRADB | 69 11% |
AS-SET
AS7641 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 71 are in fix.csv.
- Route object: none17
- Route object: RIR16
- Route object: not announced38
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 211.89.230.0/23 | No route object for it. A route object for 211.89.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.0.0/19 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.32.0/21 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.89.230.0/24 | No route object for it. A route object for 211.89.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.5.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.6.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.7.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.10.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.24.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.25.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.34.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.35.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.36.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.37.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.146.38.0/24 | No route object for it. A route object for 211.146.0.0/16 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.156.128.0/20 | No route object for it. A route object for 211.156.128.0/19 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: none | 211.156.144.0/20 | No route object for it. A route object for 211.156.128.0/19 with origin AS7641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7641 in the RIR database for the space. |
| Route object: RIR | 211.146.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.156.128.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:600::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.21.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.22.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.1.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.146.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:600:a000::/38 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:600:a600::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:600:a601::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:600:a602::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7641 whose prefix no peer sees AS7641 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 42.204.0.0/14 | NTTCOM, RADB | Valid |
| 103.8.204.0/22 | NTTCOM, RADB | Valid |
| 112.128.0.0/14 | NTTCOM, RADB | Valid |
| 117.124.0.0/14 | NTTCOM, RADB | No ROA |
| 117.127.1.0/24 | RADB | No ROA |
| 117.127.17.0/24 | RADB | No ROA |
| 117.127.117.0/24 | RADB | No ROA |
| 117.127.127.0/24 | RADB | No ROA |
| 150.242.52.0/22 | NTTCOM, RADB | Valid |
| 211.89.0.0/16 | NTTCOM, RADB | Valid |
| 211.146.0.0/16 | NTTCOM, RADB | Valid |
| 211.146.2.0/24 | RADB | Valid |
| 211.146.3.0/24 | RADB | Valid |
| 211.146.4.0/24 | RADB | Valid |
| 211.146.11.0/24 | RADB | Valid |
| 211.146.17.0/24 | RADB | Valid |
| 211.146.19.0/24 | RADB | Valid |
| 211.146.27.0/24 | RADB | Valid |
| 211.146.28.0/24 | RADB | Valid |
| 211.146.29.0/24 | RADB | Valid |
| 211.146.30.0/24 | RADB | Valid |
| 211.146.31.0/24 | RADB | Valid |
| 211.156.128.0/24 | RADB | Valid |
| 211.156.129.0/24 | RADB | Valid |
| 211.156.130.0/24 | RADB | Valid |
| 211.156.131.0/24 | RADB | Valid |
| 211.156.132.0/24 | RADB | Valid |
| 211.156.133.0/24 | RADB | Valid |
| 211.156.134.0/24 | RADB | Valid |
| 211.156.135.0/24 | RADB | Valid |
| 211.156.136.0/24 | RADB | Valid |
| 211.156.138.0/24 | RADB | Valid |
| 211.156.140.0/24 | RADB | Valid |
| 211.156.159.0/24 | RADB | Valid |
| 223.160.0.0/14 | NTTCOM, RADB | No ROA |
| 2403:600:a604::/46 | RADB | Valid |
| 2403:600:a608::/48 | RADB | Valid |
| 240a:4000::/21 | 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.