Network · data from 2026-11-12
AS149837 ChinaNet-JX-Yunhe-IDC - China Telecom
Registry name: ChinaNet-JX-Yunhe-IDC - China Telecom, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149837, 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.
| 59.63.192.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 59.63.200.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 106.227.68.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 106.227.74.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 111.74.96.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 111.79.108.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 117.21.56.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 106.227.64.0/19 | Valid | Other IRR onlyRADB | 671 100% |
| 240e:13:8800::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:960:d00::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:960:e00::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:982:7500::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:982:7600::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:982:7700::/46 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS149837 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 14 are in fix.csv.
- Route object: RIR14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 59.63.192.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 59.63.200.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.227.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.227.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.74.96.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.79.108.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.21.56.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.227.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:13:8800::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:960:d00::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:960:e00::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:7500::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:7600::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:7700::/46 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS149837 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.