Network · data from 2026-11-12
AS151823 CT-Centralsouth-China-IIP - China Telecom
Registry name: CT-Centralsouth-China-IIP - China Telecom, CN · not in PeeringDB
16IPv4 routes
100.0% RPKI valid · 0.0% with a route object
5IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
21 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS151823, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS151823, 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.
| 175.12.0.0/18 | Valid | None | 672 100% |
| 175.12.58.0/24 | Valid | None | 672 100% |
| 175.12.59.0/24 | Valid | None | 672 100% |
| 175.12.60.0/24 | Valid | None | 672 100% |
| 175.12.61.0/24 | Valid | None | 672 100% |
| 175.12.62.0/24 | Valid | None | 672 100% |
| 175.12.63.0/24 | Valid | None | 672 100% |
| 175.12.64.0/18 | Valid | None | 672 100% |
| 175.12.64.0/22 | Valid | None | 672 100% |
| 175.12.96.0/22 | Valid | None | 672 100% |
| 175.12.105.0/24 | Valid | None | 672 100% |
| 175.12.106.0/24 | Valid | None | 672 100% |
| 175.12.107.0/24 | Valid | None | 672 100% |
| 175.12.108.0/24 | Valid | None | 672 100% |
| 175.12.109.0/24 | Valid | None | 672 100% |
| 240e:106:aa00::/39 | Valid | None | 636 100% |
| 240e:96a:4000::/36 | Valid | None | 636 100% |
| 240e:982:9b00::/40 | Valid | None | 636 100% |
| 240e:982:9d00::/40 | Valid | None | 636 100% |
| 240e:982:9e00::/40 | Valid | None | 636 100% |
| 220.169.208.0/24 | Valid | None | 1 0%low visibility |
AS-SET
AS151823 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 21 are in fix.csv.
- Route object: none21
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 175.12.0.0/18 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.58.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.59.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.60.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.61.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.62.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.63.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.64.0/18 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.64.0/22 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.96.0/22 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.105.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.106.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.107.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.108.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 175.12.109.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 240e:106:aa00::/39 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 240e:96a:4000::/36 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 240e:982:9b00::/40 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 240e:982:9d00::/40 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 240e:982:9e00::/40 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
| Route object: none | 220.169.208.0/24 | No route object for it. Add a route object with origin AS151823 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS151823 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.