bgpreport

Network · data from 2026-11-12

AS139462 CHINANET-GY-AS - CHINANET Guizhou Yilong IDC

Registry name: CHINANET-GY-AS - CHINANET Guizhou Yilong IDC, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139462, 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.
58.42.112.0/20 Valid Other IRR onlyRADB 672 100% 67
111.123.40.0/21 Valid Other IRR onlyRADB 672 100% 67
218.86.240.0/22 Valid Other IRR onlyRADB 671 100% 67
240e:103:8b20::/44 Valid Other IRR onlyRADB 636 100% 68
240e:938:f900::/48 Valid Other IRR onlyRADB 636 100% 68
240e:938:f910::/44 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS139462 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 6 are in fix.csv.

  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR58.42.112.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.123.40.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.86.240.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR240e:103:8b20::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:938:f900::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:938:f910::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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