Network · data from 2026-11-12
AS22040 LINXUS1 - Linxus Internet
Registry name: LINXUS1 - Linxus Internet, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22040, 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.
| 12.50.93.0/24 | No ROA | None | 673 100% |
| 12.204.37.0/24 | No ROA | None | 673 100% |
| 12.204.39.0/24 | No ROA | None | 673 100% |
| 12.215.218.0/24 | No ROA | None | 673 100% |
| 12.215.219.0/24 | No ROA | None | 673 100% |
| 209.215.34.0/24 | No ROA | None | 2 0%low visibility |
| 12.22.114.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 12.201.111.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 12.239.213.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 72.19.2.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 169.128.252.0/22 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS22040 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: none10
- Route object: none6
- Route object: RIR4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 12.50.93.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 12.50.93.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 12.204.37.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 12.204.37.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 12.204.39.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 12.204.39.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 12.215.218.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 12.215.218.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 12.215.219.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 12.215.219.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 209.215.34.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: none | 209.215.34.0/24 | No route object for it. Add a route object with origin AS22040 in the RIR database for the space. |
| ROA: none | 12.22.114.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: RIR | 12.22.114.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 12.201.111.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: RIR | 12.201.111.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 12.239.213.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: RIR | 12.239.213.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 72.19.2.0/24 | No ROA covers it. Add a ROA for AS22040, maxLength 24. |
| Route object: RIR | 72.19.2.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22040 whose prefix no peer sees AS22040 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.133.213.0/24 | NTTCOM | 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.