Network · data from 2026-11-12
AS273250 AS273250 - SOLUCIONES DE TECNOLOGIA JAH SA DE CV
Registry name: AS273250 - SOLUCIONES DE TECNOLOGIA JAH SA DE CV, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273250, 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.
| 38.210.200.0/24 | No ROA | Nonecovered by 38.210.200.0/22 | 671 100% |
| 38.210.201.0/24 | No ROA | Nonecovered by 38.210.200.0/22 | 671 100% |
| 38.210.202.0/24 | No ROA | Nonecovered by 38.210.200.0/22 | 671 100% |
| 38.210.203.0/24 | No ROA | Nonecovered by 38.210.200.0/22 | 671 100% |
| 2806:434::/32 | No ROA | None | 636 100% |
| 200.23.120.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 200.23.126.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 200.33.72.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS273250 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 17 are in fix.csv.
- ROA: none8
- Route object: none5
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.210.200.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: none | 38.210.200.0/24 | No route object for it. A route object for 38.210.200.0/22 with origin AS273250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273250 in the RIR database for the space. |
| ROA: none | 38.210.201.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: none | 38.210.201.0/24 | No route object for it. A route object for 38.210.200.0/22 with origin AS273250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273250 in the RIR database for the space. |
| ROA: none | 38.210.202.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: none | 38.210.202.0/24 | No route object for it. A route object for 38.210.200.0/22 with origin AS273250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273250 in the RIR database for the space. |
| ROA: none | 38.210.203.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: none | 38.210.203.0/24 | No route object for it. A route object for 38.210.200.0/22 with origin AS273250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273250 in the RIR database for the space. |
| ROA: none | 2806:434::/32 | No ROA covers it. Add a ROA for AS273250, maxLength 32. |
| Route object: none | 2806:434::/32 | No route object for it. Add a route object with origin AS273250 in the RIR database for the space. |
| ROA: none | 200.23.120.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: RIR | 200.23.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.23.126.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: RIR | 200.23.126.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.33.72.0/24 | No ROA covers it. Add a ROA for AS273250, maxLength 24. |
| Route object: RIR | 200.33.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273250 whose prefix no peer sees AS273250 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.210.200.0/22 | ARIN, RADB | 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.