Network · data from 2026-11-12
AS63838 CT-HuNan-Hengyang-IDC - Hengyang
Registry name: CT-HuNan-Hengyang-IDC - Hengyang, CN · not in PeeringDB
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% |
| 113.219.166.0/23 | Valid | None | 672 100% |
| 113.219.170.0/23 | Valid | None | 672 100% |
| 113.219.172.0/23 | Valid | None | 672 100% |
| 113.219.174.0/23 | Valid | None | 672 100% |
| 113.219.176.0/23 | Valid | None | 672 100% |
| 175.4.0.0/18 | Valid | None | 672 100% |
| 175.4.24.0/22 | Valid | None | 672 100% |
| 175.6.192.0/20 | Valid | None | 672 100% |
| 175.6.208.0/21 | Valid | None | 672 100% |
| 175.6.216.0/22 | Valid | None | 672 100% |
| 175.6.216.0/23 | Valid | None | 672 100% |
| 175.6.220.0/24 | Valid | None | 672 100% |
| 175.6.224.0/19 | Valid | None | 672 100% |
| 222.243.55.0/24 | Valid | None | 672 100% |
| 222.243.56.0/24 | Valid | None | 672 100% |
| 222.245.77.0/24 | Valid | None | 672 100% |
| 203.56.216.0/24 | Valid | None | 671 100% |
| 218.77.32.0/22 | Valid | None | 671 100% |
| 113.219.128.0/18 | Valid | None | 669 99% |
| 220.170.112.0/24 | Valid | None | 669 99% |
| 240e:10:a000::/37 | Valid | None | 636 100% |
| 240e:c3:2800::/37 | Valid | None | 636 100% |
| 240e:108:1195::/48 | Valid | None | 636 100% |
| 240e:968:7000::/36 | Valid | None | 636 100% |
| 240e:982:9400::/40 | Valid | None | 636 100% |
| 240e:982:990d::/48 | Valid | None | 636 100% |
| 240e:983:1900::/48 | Valid | None | 636 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 220.170.91.0/24 | ROAs covering it name AS4134, not AS63838. If AS63838 should announce it, add a ROA for AS63838. |
| Route object: none | 220.170.91.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.166.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.170.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.172.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.174.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.176.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.4.0.0/18 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.4.24.0/22 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.192.0/20 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.208.0/21 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.216.0/22 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.216.0/23 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.220.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 175.6.224.0/19 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 222.243.55.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 222.243.56.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 222.245.77.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 203.56.216.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 218.77.32.0/22 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 113.219.128.0/18 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 220.170.112.0/24 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:10:a000::/37 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:c3:2800::/37 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:108:1195::/48 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:968:7000::/36 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:982:9400::/40 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:982:990d::/48 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
| Route object: none | 240e:983:1900::/48 | No route object for it. Add a route object with origin AS63838 in the RIR database for the space. |
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.