Network · data from 2026-11-12
AS22150 CARRIERHOUSE - Carrierhouse Corp.
Registry name: CARRIERHOUSE - Carrierhouse Corp., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22150, 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.
| 196.46.18.0/24 | No ROA | Other origin onlycovered by 196.46.18.0/23 | 667 99% |
| 196.46.19.0/24 | No ROA | Other origin onlycovered by 196.46.18.0/23 | 667 99% |
| 193.218.114.0/24 | No ROA | RIR databaseRADB, RIPE | 667 99% |
| 199.119.236.0/22 | No ROA | RIR databaseARIN | 667 99% |
| 199.204.132.0/22 | No ROA | RIR databaseARIN, RADB | 667 99% |
| 204.110.52.0/22 | No ROA | RIR databaseARIN, RADB | 667 99% |
| 208.87.0.0/22 | No ROA | RIR databaseARIN, RADB | 667 99% |
| 208.87.0.0/24 | No ROA | RIR databaseARIN | 667 99% |
| 208.87.1.0/24 | No ROA | RIR databaseARIN | 667 99% |
| 208.87.2.0/24 | No ROA | RIR databaseARIN | 667 99% |
| 208.87.3.0/24 | No ROA | RIR databaseARIN | 667 99% |
AS-SET
AS22150 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 28 are in fix.csv.
- ROA: none11
- Route object: none2
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.46.18.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| Route object: none | 196.46.18.0/24 | Route objects for it name AS33132. A route object for 196.46.18.0/23 with origin AS22150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22150 in the RIR database for the space. |
| ROA: none | 196.46.19.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| Route object: none | 196.46.19.0/24 | Route objects for it name AS33132. A route object for 196.46.18.0/23 with origin AS22150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22150 in the RIR database for the space. |
| ROA: none | 193.218.114.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| ROA: none | 199.119.236.0/22 | No ROA covers it. Add a ROA for AS22150, maxLength 22. |
| ROA: none | 199.204.132.0/22 | No ROA covers it. Add a ROA for AS22150, maxLength 22. |
| ROA: none | 204.110.52.0/22 | No ROA covers it. Add a ROA for AS22150, maxLength 22. |
| ROA: none | 208.87.0.0/22 | No ROA covers it. Add a ROA for AS22150, maxLength 22. |
| ROA: none | 208.87.0.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| ROA: none | 208.87.1.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| ROA: none | 208.87.2.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
| ROA: none | 208.87.3.0/24 | No ROA covers it. Add a ROA for AS22150, maxLength 24. |
Route objects not announced
Route objects with origin AS22150 whose prefix no peer sees AS22150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 196.46.18.0/23 | RADB | No ROA |
| 199.119.236.0/24 | ARIN | No ROA |
| 199.119.237.0/24 | ARIN | No ROA |
| 199.119.239.0/24 | ARIN | No ROA |
| 199.204.132.0/24 | ARIN | No ROA |
| 199.204.133.0/24 | ARIN | No ROA |
| 199.204.134.0/24 | ARIN | No ROA |
| 199.204.135.0/24 | ARIN | No ROA |
| 204.110.52.0/23 | ARIN, RADB | No ROA |
| 204.110.52.0/24 | ARIN, RADB | No ROA |
| 204.110.53.0/24 | ARIN, RADB | No ROA |
| 204.110.54.0/23 | ARIN, RADB | No ROA |
| 204.110.54.0/24 | ARIN, RADB | No ROA |
| 204.110.55.0/24 | ARIN, RADB | No ROA |
| 2602:fd06::/36 | 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.