Network · data from 2026-11-12
AS132510 ShanXiMCC-IDC - IDC ShanXi China Mobile communications corporation
Registry name: ShanXiMCC-IDC - IDC ShanXi China Mobile communications corporation, CN · not in PeeringDB
25IPv4 routes
100.0% RPKI valid · 100.0% with a route object
4IPv6 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
5Route objects not announced
registered with origin AS132510, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS132510, 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.
| 183.201.46.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.64.0/18 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.64.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.195.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.228.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.252.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.201.254.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.0.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 183.203.18.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.20.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.64.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.82.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.84.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.88.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.92.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.94.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.96.0/21 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.104.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 183.203.112.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 211.142.22.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.142.30.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 221.180.20.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 221.180.22.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 183.201.192.0/18 | Valid | Other IRR onlyRADB | 670 100% |
| 2409:800c:3001::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2409:800c:3002::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2409:8c0c:200::/40 | Valid | Other IRR onlyRADB | 634 100% |
| 2409:8c0c:300::/40 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS132510 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 34 are in fix.csv.
- Route object: RIR29
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 183.201.46.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.64.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.195.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.228.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.252.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.0.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.18.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.82.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.84.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.88.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.92.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.94.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.96.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.104.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.203.112.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.142.22.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.142.30.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.180.20.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.180.22.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.201.192.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2409:800c:3001::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2409:800c:3002::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2409:8c0c:200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2409:8c0c:300::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132510 whose prefix no peer sees AS132510 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 183.203.0.0/16 | NTTCOM, RADB | No ROA |
| 183.203.64.0/18 | NTTCOM, RADB | No ROA |
| 211.142.0.0/18 | NTTCOM, RADB | No ROA |
| 211.142.30.0/23 | NTTCOM, RADB | No ROA |
| 221.180.0.0/18 | NTTCOM, RADB | No ROA |
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.