bgpreport

Network · data from 2026-11-12

AS146838 CHINABTN - China Broadcasting TV Net

Registry name: CHINABTN - China Broadcasting TV Net, CN · not in PeeringDB

12IPv4 routes 100.0% RPKI valid · 0.0% with a route object
3IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 15 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS146838, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS146838, 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.
117.126.0.0/17 Valid None 84 12% 37
117.126.3.0/24 Valid None 84 12% 37
117.126.4.0/23 Valid Nonecovered by 117.126.4.0/22 84 12% 37
117.126.6.0/24 Valid Nonecovered by 117.126.4.0/22 84 12% 37
117.126.7.0/24 Valid Nonecovered by 117.126.4.0/22 84 12% 37
117.126.8.0/21 Valid None 84 12% 37
117.126.24.0/21 Valid None 84 12% 37
117.126.128.0/17 Valid None 84 12% 37
117.126.128.0/21 Valid None 84 12% 37
117.126.240.0/21 Valid None 84 12% 37
117.126.250.0/23 Valid None 84 12% 37
117.126.254.0/24 Valid None 84 12% 37
240a:4093::/35 Valid None 69 11% 34
240a:41d6::/31 Valid None 69 11% 34
240a:4230::/31 Valid None 69 11% 34

AS-SET

AS146838 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: none15
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none117.126.0.0/17No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.3.0/24No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.4.0/23No route object for it. A route object for 117.126.4.0/22 with origin AS146838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.6.0/24No route object for it. A route object for 117.126.4.0/22 with origin AS146838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.7.0/24No route object for it. A route object for 117.126.4.0/22 with origin AS146838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.8.0/21No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.24.0/21No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.128.0/17No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.128.0/21No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.240.0/21No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.250.0/23No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none117.126.254.0/24No route object for it. Add a route object with origin AS146838 in the RIR database for the space.84 of 673
Route object: none240a:4093::/35No route object for it. Add a route object with origin AS146838 in the RIR database for the space.69 of 636
Route object: none240a:41d6::/31No route object for it. Add a route object with origin AS146838 in the RIR database for the space.69 of 636
Route object: none240a:4230::/31No route object for it. Add a route object with origin AS146838 in the RIR database for the space.69 of 636

Route objects not announced

Route objects with origin AS146838 whose prefix no peer sees AS146838 announce. Many are kept on purpose (backup routes, space announced only in some places).

117.126.4.0/22APNICValid

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.