Network · data from 2026-11-12
AS266836 COOPERATIVA DE PROVISION DE ELECTRICIDAD Y SERVICIOS PUBLICOS GENERAL CABRERA
Registry name: AS266836 - COOPERATIVA DE PROVISION DE ELECTRICIDAD Y SERVICIOS PUBLICOS GENERAL CABRERA LIMITADA, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266836, 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.191.47.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 38.210.8.0/24 | Valid | Nonecovered by 38.210.8.0/22 | 669 99% |
| 38.210.9.0/24 | Valid | Nonecovered by 38.210.8.0/22 | 669 99% |
| 38.210.10.0/24 | Valid | Nonecovered by 38.210.8.0/22 | 669 99% |
| 38.210.11.0/24 | Valid | Nonecovered by 38.210.8.0/22 | 669 99% |
| 45.238.16.0/24 | Valid | Nonecovered by 45.238.16.0/22 | 143 21% |
| 45.238.17.0/24 | Valid | Nonecovered by 45.238.16.0/22 | 143 21% |
| 45.238.18.0/24 | Valid | Nonecovered by 45.238.16.0/22 | 143 21% |
| 45.238.19.0/24 | Valid | Nonecovered by 45.238.16.0/22 | 143 21% |
| 45.238.16.0/22 | Valid | RIR databaseLACNIC | 673 100% |
AS-SET
AS266836's PeeringDB record names no 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 11 are in fix.csv.
- ROA: none1
- Route object: none8
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.191.47.0/24 | No ROA covers it. Add a ROA for AS266836, maxLength 24. |
| Route object: RIR | 38.191.47.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 38.210.8.0/24 | No route object for it. A route object for 38.210.8.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 38.210.9.0/24 | No route object for it. A route object for 38.210.8.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 38.210.10.0/24 | No route object for it. A route object for 38.210.8.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 38.210.11.0/24 | No route object for it. A route object for 38.210.8.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 45.238.16.0/24 | No route object for it. A route object for 45.238.16.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 45.238.17.0/24 | No route object for it. A route object for 45.238.16.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 45.238.18.0/24 | No route object for it. A route object for 45.238.16.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
| Route object: none | 45.238.19.0/24 | No route object for it. A route object for 45.238.16.0/22 with origin AS266836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266836 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266836 whose prefix no peer sees AS266836 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.210.8.0/22 | ARIN | 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.