bgpreport

Network · data from 2026-11-12

AS63838 CT-HuNan-Hengyang-IDC - Hengyang

Registry name: CT-HuNan-Hengyang-IDC - Hengyang, CN · not in PeeringDB

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

Announced routes

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

220.170.91.0/24 Invalid: origin None 126 19% 51
113.219.166.0/23 Valid None 672 100% 67
113.219.170.0/23 Valid None 672 100% 67
113.219.172.0/23 Valid None 672 100% 67
113.219.174.0/23 Valid None 672 100% 67
113.219.176.0/23 Valid None 672 100% 67
175.4.0.0/18 Valid None 672 100% 67
175.4.24.0/22 Valid None 672 100% 67
175.6.192.0/20 Valid None 672 100% 67
175.6.208.0/21 Valid None 672 100% 67
175.6.216.0/22 Valid None 672 100% 67
175.6.216.0/23 Valid None 672 100% 67
175.6.220.0/24 Valid None 672 100% 67
175.6.224.0/19 Valid None 672 100% 67
222.243.55.0/24 Valid None 672 100% 67
222.243.56.0/24 Valid None 672 100% 67
222.245.77.0/24 Valid None 672 100% 67
203.56.216.0/24 Valid None 671 100% 67
218.77.32.0/22 Valid None 671 100% 67
113.219.128.0/18 Valid None 669 99% 67
220.170.112.0/24 Valid None 669 99% 67
240e:10:a000::/37 Valid None 636 100% 68
240e:c3:2800::/37 Valid None 636 100% 68
240e:108:1195::/48 Valid None 636 100% 68
240e:968:7000::/36 Valid None 636 100% 68
240e:982:9400::/40 Valid None 636 100% 68
240e:982:990d::/48 Valid None 636 100% 68
240e:983:1900::/48 Valid None 636 100% 68

AS-SET

AS63838 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 29 are in fix.csv.

  • ROA: origin1
  • Route object: none28
ChangePrefix or setDetailFull-table peers
ROA: origin220.170.91.0/24ROAs covering it name AS4134, not AS63838. If AS63838 should announce it, add a ROA for AS63838.126 of 673
Route object: none220.170.91.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.126 of 673
Route object: none113.219.166.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none113.219.170.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none113.219.172.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none113.219.174.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none113.219.176.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.4.0.0/18No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.4.24.0/22No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.192.0/20No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.208.0/21No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.216.0/22No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.216.0/23No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.220.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none175.6.224.0/19No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none222.243.55.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none222.243.56.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none222.245.77.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.672 of 673
Route object: none203.56.216.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.671 of 673
Route object: none218.77.32.0/22No route object for it. Add a route object with origin AS63838 in the RIR database for the space.671 of 673
Route object: none113.219.128.0/18No route object for it. Add a route object with origin AS63838 in the RIR database for the space.669 of 673
Route object: none220.170.112.0/24No route object for it. Add a route object with origin AS63838 in the RIR database for the space.669 of 673
Route object: none240e:10:a000::/37No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:c3:2800::/37No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:108:1195::/48No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:968:7000::/36No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:982:9400::/40No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:982:990d::/48No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636
Route object: none240e:983:1900::/48No route object for it. Add a route object with origin AS63838 in the RIR database for the space.636 of 636

Route objects not announced

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