Network · data from 2026-11-12

AS38355 CNT - ChongQing Broadcast & TV Broadband IP MAN

Registry name: CNT - ChongQing Broadcast & TV Broadband IP MAN, CN · not in PeeringDB

0IPv4 routes

4IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

4Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS38355, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38355, 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.


2401:7e00:fff8::/45	Valid	Nonecovered by 2401:7e00::/32	43 7%low visibility	30
2401:7e00:ffff::/48	Valid	Nonecovered by 2401:7e00::/32	43 7%low visibility	30
2401:7e00::/32	Valid	Other IRR onlyRADB	44 7%low visibility	30
2401:7e00::/36	Valid	Other IRR onlyRADB	44 7%low visibility	30

2401:7e00:fff8::/45

Valid

Nonecovered by 2401:7e00::/32

43 7%low visibility

2401:7e00:ffff::/48

Valid

Nonecovered by 2401:7e00::/32

43 7%low visibility

2401:7e00::/32

Valid

Other IRR onlyRADB

44 7%low visibility

2401:7e00::/36

Valid

Other IRR onlyRADB

44 7%low visibility

AS-SET

AS38355 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 4 are in fix.csv.

Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2401:7e00:fff8::/45	No route object for it. A route object for 2401:7e00::/32 with origin AS38355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38355 in the RIR database for the space.	43 of 636
Route object: none	2401:7e00:ffff::/48	No route object for it. A route object for 2401:7e00::/32 with origin AS38355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38355 in the RIR database for the space.	43 of 636
Route object: RIR	2401:7e00::/32	Route object only in RADB. Add it in the RIR database for the space.	44 of 636
Route object: RIR	2401:7e00::/36	Route object only in RADB. Add it in the RIR database for the space.	44 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2401:7e00:fff8::/45

No route object for it. A route object for 2401:7e00::/32 with origin AS38355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38355 in the RIR database for the space.

43 of 636

Route object: none

2401:7e00:ffff::/48

43 of 636

Route object: RIR

2401:7e00::/32

Route object only in RADB. Add it in the RIR database for the space.

44 of 636

Route object: RIR

2401:7e00::/36

Route object only in RADB. Add it in the RIR database for the space.

44 of 636

Route objects not announced

Every route object with origin AS38355 is announced.

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.