bgpreport

Network · data from 2026-11-12

AS58852 GZGD - Guizhou provincial radio and television information Network Inc

Registry name: GZGD - Guizhou provincial radio and television information Network Inc, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58852, 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.85.147.0/24 Valid None 84 12% 37
103.242.212.0/22 Valid None 63 9%low visibility 33
203.189.240.0/22 Valid None 63 9%low visibility 33
2402:6fc0::/48 Valid None 43 7%low visibility 30

AS-SET

AS58852 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: none4
ChangePrefix or setDetailFull-table peers
Route object: none103.85.147.0/24No route object for it. Add a route object with origin AS58852 in the RIR database for the space.84 of 673
Route object: none103.242.212.0/22No route object for it. Add a route object with origin AS58852 in the RIR database for the space.63 of 673
Route object: none203.189.240.0/22No route object for it. Add a route object with origin AS58852 in the RIR database for the space.63 of 673
Route object: none2402:6fc0::/48No route object for it. Add a route object with origin AS58852 in the RIR database for the space.43 of 636

Route objects not announced

Every route object with origin AS58852 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.