bgpreport

Network · data from 2026-11-12

AS139203 Guizhou GuiAn IDC

Registry name: CHINANET-Guizhou-Guian-IDC - Guizhou GuiAn IDC, CN · PeeringDB

20IPv4 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 AS139203, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139203, 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.2.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.5.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.9.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.10.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.14.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.15.0/24 Valid Other IRR onlyRADB 672 100% 67
58.42.48.0/20 Valid Other IRR onlyRADB 672 100% 67
106.108.56.0/21 Valid Other IRR onlyRADB 672 100% 67
106.108.72.0/21 Valid Other IRR onlyRADB 672 100% 67
106.108.88.0/21 Valid Other IRR onlyRADB 672 100% 67
111.123.53.0/24 Valid Other IRR onlyRADB 672 100% 67
111.123.54.0/24 Valid Other IRR onlyRADB 672 100% 67
111.123.55.0/24 Valid Other IRR onlyRADB 672 100% 67
111.123.56.0/21 Valid Other IRR onlyRADB 672 100% 67
111.124.64.0/20 Valid Other IRR onlyRADB 672 100% 67
111.124.76.0/24 Valid Other IRR onlyRADB 672 100% 67
111.124.144.0/24 Valid Other IRR onlyRADB 672 100% 67
111.124.192.0/19 Valid Other IRR onlyRADB 672 100% 67
58.42.8.0/21 Valid Other IRR onlyRADB 671 100% 67
119.0.64.0/19 Valid Other IRR onlyRADB 669 99% 67
240e:103:8b00::/44 Valid Other IRR onlyRADB 636 100% 68
240e:938:a00::/44 Valid Other IRR onlyRADB 636 100% 68
240e:938:a03::/48 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS139203's PeeringDB record names no 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 23 are in fix.csv.

  • Route object: RIR23
ChangePrefix or setDetailFull-table peers
Route object: RIR58.42.2.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.10.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.48.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.108.56.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.108.72.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.108.88.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.123.53.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.123.54.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.123.55.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.123.56.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.124.64.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.124.76.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.124.144.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR111.124.192.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.42.8.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR119.0.64.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR240e:103:8b00::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:938:a00::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:938:a03::/48Route 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 AS139203 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.