Network · data from 2026-11-12
AS64105 Cabase RGL RS
Registry name: AS64105 - CABASE Camara Arg de Base de Datos y Serv en Linea, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64105, 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.
| 138.204.252.0/24 | Valid | RIR databaseLACNIC | 8 1%low visibility |
| 2001:13c7:601e::/48 | Valid | RIR databaseLACNIC | 8 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS64105: AS64105:AS-RGL. 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 (AS64105 isn't in the set, or no route object for AS64105 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 | AS64105 in it | Not covered |
|---|---|---|---|---|---|
| AS64105:AS-RGL | LACNIC | 1 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS64105 is announced.
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.