Network · data from 2026-11-12
AS272848 HUASCARAN INTERNET
Registry name: AS272848 - HUASCARAN INVESTMENT GROUP S.A.C., PE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272848, 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.
| 9.8.8.0/24 | No ROA | None | 29 4%low visibility |
| 170.80.172.0/24 | No ROA | Other origin only | 29 4%low visibility |
| 2900:abcd::/32 | No ROA | None | 23 4%low visibility |
| 2803:b0e0:26a2::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 38.56.97.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 38.56.107.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 2803:5200:6412::/48 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:cd60:5022::/48 | Valid | RIR databaseLACNIC | 634 100% |
| 201.218.133.0/24 | Valid | RIR databaseLACNIC, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS272848: AS-HUASCARAN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS272848 isn't in the set, or no route object for AS272848 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS272848 in it | Not covered |
|---|---|---|---|---|---|
| AS-HUASCARAN | RADB | 4 | 1 | Yes | 3 |
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: none3
- Route object: none3
- Route object: RIR1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 9.8.8.0/24 | No ROA covers it. Add a ROA for AS272848, maxLength 24. |
| Route object: none | 9.8.8.0/24 | No route object for it. Add a route object with origin AS272848 in the RIR database for the space. |
| ROA: none | 170.80.172.0/24 | No ROA covers it. Add a ROA for AS272848, maxLength 24. |
| Route object: none | 170.80.172.0/24 | Route objects for it name AS52447. Add a route object with origin AS272848 in the RIR database for the space. |
| ROA: none | 2900:abcd::/32 | No ROA covers it. Add a ROA for AS272848, maxLength 32. |
| Route object: none | 2900:abcd::/32 | No route object for it. Add a route object with origin AS272848 in the RIR database for the space. |
| Route object: RIR | 2803:b0e0:26a2::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS272848 whose prefix no peer sees AS272848 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 201.218.132.0/24 | LACNIC, RADB | Valid |
| 201.218.139.0/24 | LACNIC, RADB | Valid |
| 201.218.142.0/23 | LACNIC, RADB | Valid |
| 201.218.142.0/24 | RADB | Valid |
| 201.218.143.0/24 | RADB | Valid |
| 201.218.148.0/24 | LACNIC | Valid |
| 201.218.153.0/24 | LACNIC, RADB | Valid |
| 2803:5200:6413::/48 | LACNIC, RADB | Valid |
| 2803:cd60:6414::/48 | LACNIC, RADB | Valid |
| 2803:cd60:6420::/48 | LACNIC, RADB | 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.