Network · data from 2026-11-12
AS262150 EPEC Telecomunicaciones
Registry name: AS262150 - Empresa Provincial de Energia de Cordoba, AR · PeeringDB
24IPv4 routes
100.0% RPKI valid · 0.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
24 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS262150, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS262150, 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.
| 131.72.204.0/24 | Valid | Nonecovered by 131.72.204.0/22 | 671 100% |
| 131.72.206.0/24 | Valid | Nonecovered by 131.72.204.0/22 | 671 100% |
| 190.96.113.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.114.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.116.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.117.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.118.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.119.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.120.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.121.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.122.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.123.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.124.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.125.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.126.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 190.96.127.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 671 100% |
| 200.105.104.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 671 100% |
| 200.105.105.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 671 100% |
| 200.105.107.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 671 100% |
| 200.105.111.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 671 100% |
| 190.96.112.0/24 | Valid | Nonecovered by 190.96.112.0/20 | 670 100% |
| 200.105.108.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 670 100% |
| 200.105.110.0/24 | Valid | Nonecovered by 200.105.104.0/21 | 670 100% |
| 131.72.205.0/24 | Valid | Nonecovered by 131.72.204.0/22 | 669 99% |
| 2803:7300::/32 | Valid | RIR databaseLACNIC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS262150: LACNIC::AS262150:AS-CBAEPEC. 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 (AS262150 isn't in the set, or no route object for AS262150 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 | AS262150 in it | Not covered |
|---|---|---|---|---|---|
| LACNIC::AS262150:AS-CBAEPEC | LACNIC | 16 | 1 | No | 25 |
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 28 are in fix.csv.
- Route object: none24
- AS-SET: own ASN1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.72.204.0/24 | No route object for it. A route object for 131.72.204.0/22 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 131.72.206.0/24 | No route object for it. A route object for 131.72.204.0/22 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.113.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.114.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.116.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.117.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.118.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.119.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.120.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.121.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.122.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.123.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.124.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.125.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.126.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.127.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.104.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.105.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.107.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.111.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 190.96.112.0/24 | No route object for it. A route object for 190.96.112.0/20 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.108.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 200.105.110.0/24 | No route object for it. A route object for 200.105.104.0/21 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| Route object: none | 131.72.205.0/24 | No route object for it. A route object for 131.72.204.0/22 with origin AS262150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262150 in the RIR database for the space. |
| AS-SET: own ASN | LACNIC::AS262150:AS-CBAEPEC | AS262150 isn't in AS262150:AS-CBAEPEC (LACNIC) once expanded. Add AS262150 to it. |
Route objects not announced
Route objects with origin AS262150 whose prefix no peer sees AS262150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.72.204.0/22 | LACNIC | Valid |
| 190.96.112.0/20 | LACNIC | Valid |
| 200.105.104.0/21 | 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.