Network · data from 2026-11-12
AS151185 CT-XIANGYANG-IDC2 - China Telecom
Registry name: CT-XIANGYANG-IDC2 - China Telecom, CN · not in PeeringDB
26IPv4 routes
100.0% RPKI valid · 100.0% with a route object
9IPv6 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 AS151185, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS151185, 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.
| 43.226.49.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 43.226.72.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 43.227.68.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 43.227.80.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 61.184.0.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 61.184.16.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.20.128.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.65.224.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 103.255.68.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 111.170.0.0/18 | Valid | Other IRR onlyRADB | 672 100% |
| 111.170.32.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 111.170.48.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 111.170.129.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 111.170.232.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 171.80.0.0/18 | Valid | Other IRR onlyRADB | 672 100% |
| 171.80.64.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 171.80.96.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 171.80.112.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 61.184.8.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 61.184.20.0/22 | Valid | Other IRR onlyRADB | 669 99% |
| 103.45.128.0/19 | Valid | Other IRR onlyRADB | 669 99% |
| 111.170.0.0/20 | Valid | Other IRR onlyRADB | 669 99% |
| 111.170.16.0/20 | Valid | Other IRR onlyRADB | 669 99% |
| 111.170.128.0/20 | Valid | Other IRR onlyRADB | 669 99% |
| 111.170.144.0/20 | Valid | Other IRR onlyRADB | 669 99% |
| 111.170.160.0/20 | Valid | Other IRR onlyRADB | 669 99% |
| 2401:5c20:10::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:105:f100::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:1162::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:1166::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:4306::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:108:4b06::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:95d:c00::/38 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:982:6200::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:982:6600::/40 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS151185 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 35 are in fix.csv.
- Route object: RIR35
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 43.226.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.226.72.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.227.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.227.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.184.0.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.184.16.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.20.128.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.65.224.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.255.68.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.0.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.32.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.232.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 171.80.0.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 171.80.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 171.80.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 171.80.112.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.184.8.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.184.20.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.45.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.16.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.128.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.144.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.170.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:5c20:10::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:105:f100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:1162::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:1166::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:4306::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:108:4b06::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:95d:c00::/38 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:6200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:6600::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS151185 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.