Network · data from 2026-11-12
AS20111 LENOVO-NET - Lenovo (United States) Inc.
Registry name: LENOVO-NET - Lenovo (United States) Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20111, 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.
| 104.232.232.0/24 | No ROA | Other origin only | 669 99% |
| 104.232.233.0/24 | No ROA | Other origin only | 669 99% |
| 104.232.224.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 104.232.228.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 144.188.129.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 144.188.134.0/24 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS20111 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 22 are in fix.csv.
- ROA: none6
- Route object: none2
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.232.232.0/24 | No ROA covers it. Add a ROA for AS20111, maxLength 24. |
| Route object: none | 104.232.232.0/24 | Route objects for it name AS138005. Add a route object with origin AS20111 in the RIR database for the space. |
| ROA: none | 104.232.233.0/24 | No ROA covers it. Add a ROA for AS20111, maxLength 24. |
| Route object: none | 104.232.233.0/24 | Route objects for it name AS138005. Add a route object with origin AS20111 in the RIR database for the space. |
| ROA: none | 104.232.224.0/23 | No ROA covers it. Add a ROA for AS20111, maxLength 23. |
| ROA: none | 104.232.228.0/24 | No ROA covers it. Add a ROA for AS20111, maxLength 24. |
| ROA: none | 144.188.129.0/24 | No ROA covers it. Add a ROA for AS20111, maxLength 24. |
| ROA: none | 144.188.134.0/24 | No ROA covers it. Add a ROA for AS20111, maxLength 24. |
Route objects not announced
Route objects with origin AS20111 whose prefix no peer sees AS20111 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.30.232.0/24 | APNIC | Valid |
| 103.30.233.0/24 | APNIC | Valid |
| 104.232.224.0/24 | ARIN | No ROA |
| 104.232.225.0/24 | ARIN | No ROA |
| 104.232.253.0/24 | ARIN | No ROA |
| 104.232.254.0/24 | ARIN | No ROA |
| 104.232.255.0/24 | ARIN | No ROA |
| 144.188.20.0/24 | ARIN | No ROA |
| 144.188.28.0/24 | ARIN | No ROA |
| 144.188.64.0/20 | ARIN | No ROA |
| 144.188.128.0/24 | ARIN | No ROA |
| 144.188.130.0/24 | ARIN | No ROA |
| 144.188.131.0/24 | ARIN | No ROA |
| 144.189.129.0/24 | ARIN | 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.