Network · data from 2026-11-12
AS64161 AS64161 - GRUPO ZGH SPA
Registry name: AS64161 - GRUPO ZGH SPA, CL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64161, 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.
| 195.88.213.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 38.20.7.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.0.201.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 166.0.14.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 188.255.170.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 72.11.131.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
AS64161 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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 195.88.213.0/24 | ROAs covering it name AS215294, not AS64161. If AS64161 should announce it, add a ROA for AS64161. |
| Route object: none | 195.88.213.0/24 | Route objects for it name AS215294. Add a route object with origin AS64161 in the RIR database for the space. |
| ROA: none | 38.20.7.0/24 | No ROA covers it. Add a ROA for AS64161, maxLength 24. |
| Route object: RIR | 38.20.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS64161 whose prefix no peer sees AS64161 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.162.184.0/22 | LACNIC | Valid |
| 2803:49a0::/32 | LACNIC | Valid |
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.