Network · data from 2026-11-12
AS133118 UNICOM-CN - China Unicom IP network
Registry name: UNICOM-CN - China Unicom IP network, CN · not in PeeringDB
18IPv4 routes
83.3% RPKI valid · 50.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
2No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS133118, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS133118, 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.
| 103.241.95.0/24 | Invalid: origin | None | 82 12% |
| 103.212.4.0/22 | No ROA | None | 161 24% |
| 146.196.116.0/22 | No ROA | None | 115 17% |
| 103.224.232.0/24 | Valid | None | 673 100% |
| 106.74.24.0/24 | Valid | Nonecovered by 106.74.0.0/17 | 673 100% |
| 106.74.25.0/24 | Valid | Nonecovered by 106.74.0.0/17 | 673 100% |
| 106.74.26.0/24 | Valid | Nonecovered by 106.74.0.0/17 | 673 100% |
| 106.74.27.0/24 | Valid | Nonecovered by 106.74.0.0/17 | 673 100% |
| 106.74.32.0/24 | Valid | Nonecovered by 106.74.0.0/17 | 673 100% |
| 103.224.233.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.224.234.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.224.235.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.243.136.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.243.137.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.243.138.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.243.139.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 106.74.0.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 106.74.128.0/17 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 2408:877d::/32 | Valid | RIR databaseAPNIC | 629 99% |
AS-SET
AS133118 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.
- ROA: origin1
- ROA: none2
- Route object: none9
- Route object: RIR9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.241.95.0/24 | ROAs covering it name AS59010, not AS133118. If AS133118 should announce it, add a ROA for AS133118. |
| Route object: none | 103.241.95.0/24 | No route object for it. Add a route object with origin AS133118 in the RIR database for the space. |
| ROA: none | 103.212.4.0/22 | No ROA covers it. Add a ROA for AS133118, maxLength 22. |
| Route object: none | 103.212.4.0/22 | No route object for it. Add a route object with origin AS133118 in the RIR database for the space. |
| ROA: none | 146.196.116.0/22 | No ROA covers it. Add a ROA for AS133118, maxLength 22. |
| Route object: none | 146.196.116.0/22 | No route object for it. Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 103.224.232.0/24 | No route object for it. Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 106.74.24.0/24 | No route object for it. A route object for 106.74.0.0/17 with origin AS133118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 106.74.25.0/24 | No route object for it. A route object for 106.74.0.0/17 with origin AS133118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 106.74.26.0/24 | No route object for it. A route object for 106.74.0.0/17 with origin AS133118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 106.74.27.0/24 | No route object for it. A route object for 106.74.0.0/17 with origin AS133118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: none | 106.74.32.0/24 | No route object for it. A route object for 106.74.0.0/17 with origin AS133118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133118 in the RIR database for the space. |
| Route object: RIR | 103.224.233.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.224.234.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.224.235.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.243.136.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.243.137.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.243.138.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.243.139.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.74.0.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 106.74.128.0/17 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS133118 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.