Network · data from 2026-11-12
AS10212 CHINAENTERCOM - China Enterprise ICT Solutions Limited
Registry name: CHINAENTERCOM - China Enterprise ICT Solutions Limited, CN · not in PeeringDB
40IPv4 routes
100.0% RPKI valid · 37.5% with a route object
2IPv6 routes
100.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
26 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS10212, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS10212, 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.
| 210.5.7.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.9.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.10.0/23 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.16.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.18.0/23 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.20.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.27.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.28.0/23 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 210.5.30.0/24 | Valid | Nonecovered by 210.5.0.0/19 | 671 100% |
| 218.96.64.0/22 | Valid | Nonecovered by 218.96.0.0/16 | 671 100% |
| 218.96.104.0/22 | Valid | Nonecovered by 218.96.0.0/16 | 670 100% |
| 218.96.108.0/23 | Valid | Nonecovered by 218.96.0.0/16 | 670 100% |
| 218.96.244.0/24 | Valid | Nonecovered by 218.96.0.0/16 | 670 100% |
| 218.96.255.0/24 | Valid | Nonecovered by 218.96.0.0/16 | 670 100% |
| 218.97.16.0/24 | Valid | Nonecovered by 218.97.0.0/19 | 670 100% |
| 218.97.0.0/21 | Valid | Nonecovered by 218.97.0.0/20 | 667 99% |
| 218.97.21.0/24 | Valid | Nonecovered by 218.97.0.0/19 | 666 99% |
| 218.96.64.0/24 | Valid | Nonecovered by 218.96.0.0/16 | 660 98% |
| 218.96.65.0/24 | Valid | Nonecovered by 218.96.0.0/16 | 660 98% |
| 218.96.107.0/24 | Valid | Nonecovered by 218.96.0.0/16 | 660 98% |
| 218.97.30.0/24 | Valid | Nonecovered by 218.97.0.0/19 | 660 98% |
| 218.97.39.0/24 | Valid | Nonecovered by 218.97.32.0/19 | 660 98% |
| 2403:b400:4000::/36 | Valid | Nonecovered by 2403:b400::/32 | 636 100% |
| 218.96.71.0/24 | Valid | Other origin onlycovered by 218.96.0.0/16 | 113 17% |
| 218.97.4.0/24 | Valid | Nonecovered by 218.97.0.0/20 | 30 4%low visibility |
| 218.97.14.0/24 | Valid | Nonecovered by 218.97.0.0/20 | 30 4%low visibility |
| 183.91.144.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 183.91.144.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 183.91.152.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 210.5.25.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 218.96.241.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 210.5.0.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.5.22.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.96.0.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.0.0/18 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.0.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.0.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.15.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 218.97.32.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 2403:b400::/32 | Valid | Other IRR onlyNTTCOM, RADB | 636 100% |
| 218.96.128.0/24 | Valid | Other IRR onlyRADB | 130 19% |
AS-SET
AS10212 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 43 are in fix.csv.
- Route object: none26
- Route object: RIR16
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 210.5.7.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.9.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.10.0/23 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.16.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.18.0/23 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.20.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.27.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.28.0/23 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 210.5.30.0/24 | No route object for it. A route object for 210.5.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.64.0/22 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.104.0/22 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.108.0/23 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.244.0/24 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.255.0/24 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.16.0/24 | No route object for it. A route object for 218.97.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.0.0/21 | No route object for it. A route object for 218.97.0.0/20 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.21.0/24 | No route object for it. A route object for 218.97.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.64.0/24 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.65.0/24 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.107.0/24 | No route object for it. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.30.0/24 | No route object for it. A route object for 218.97.0.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.39.0/24 | No route object for it. A route object for 218.97.32.0/19 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 2403:b400:4000::/36 | No route object for it. A route object for 2403:b400::/32 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.96.71.0/24 | Route objects for it name AS134774. A route object for 218.96.0.0/16 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.4.0/24 | No route object for it. A route object for 218.97.0.0/20 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: none | 218.97.14.0/24 | No route object for it. A route object for 218.97.0.0/20 with origin AS10212 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10212 in the RIR database for the space. |
| Route object: RIR | 183.91.144.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.91.144.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.91.152.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.5.25.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.96.241.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.5.0.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.5.22.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.96.0.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.0.0/18 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.0.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.0.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.97.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:b400::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.96.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10212 whose prefix no peer sees AS10212 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 218.96.0.0/16 | NTTCOM, RADB | Valid |
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.