Network · data from 2026-11-12
AS27851 Coop. Eléctrica y de Servicios Públicos Luján
Registry name: AS27851 - COOPERATIVA ELECTRICA Y DE SERVICIOS PUBLICOS LUJANENSE LIMITADA, AR · PeeringDB
23IPv4 routes
100.0% RPKI valid · 17.4% with a route object
5IPv6 routes
100.0% RPKI valid · 20.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
23 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS27851, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27851, 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.
| 2803:3680::/48 | Valid | Nonecovered by 2803:3680::/32 | 320 50% |
| 2803:3680:2::/48 | Valid | Nonecovered by 2803:3680::/32 | 320 50% |
| 2803:3680:3::/48 | Valid | Nonecovered by 2803:3680::/32 | 320 50% |
| 2803:3680:7f00::/40 | Valid | Nonecovered by 2803:3680::/32 | 320 50% |
| 170.231.36.0/24 | Valid | Nonecovered by 170.231.36.0/22 | 102 15% |
| 170.231.37.0/24 | Valid | Nonecovered by 170.231.36.0/22 | 102 15% |
| 170.231.38.0/24 | Valid | Nonecovered by 170.231.36.0/22 | 102 15% |
| 170.231.39.0/24 | Valid | Nonecovered by 170.231.36.0/22 | 102 15% |
| 200.81.152.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.153.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.154.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.155.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.156.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.157.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.158.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.81.159.0/24 | Valid | Nonecovered by 200.81.152.0/21 | 102 15% |
| 200.110.185.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.186.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.187.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.188.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.189.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.190.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.191.0/24 | Valid | Nonecovered by 200.110.184.0/21 | 102 15% |
| 200.110.184.0/24 | Valid | Other IRR onlyALTDB | 98 15% |
| 170.231.36.0/22 | Valid | RIR databaseALTDB, LACNIC | 672 100% |
| 200.81.152.0/21 | Valid | RIR databaseALTDB, LACNIC | 671 100% |
| 200.110.184.0/21 | Valid | RIR databaseALTDB, LACNIC | 671 100% |
| 2803:3680::/32 | Valid | RIR databaseALTDB, LACNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS27851: LACNIC::AS27851:AS-COOPENET. 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 (AS27851 isn't in the set, or no route object for AS27851 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 | AS27851 in it | Not covered |
|---|---|---|---|---|---|
| LACNIC::AS27851:AS-COOPENET | LACNIC | 20 | 1 | Yes | 0 |
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 24 are in fix.csv.
- Route object: none23
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:3680::/48 | No route object for it. A route object for 2803:3680::/32 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 2803:3680:2::/48 | No route object for it. A route object for 2803:3680::/32 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 2803:3680:3::/48 | No route object for it. A route object for 2803:3680::/32 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 2803:3680:7f00::/40 | No route object for it. A route object for 2803:3680::/32 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 170.231.36.0/24 | No route object for it. A route object for 170.231.36.0/22 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 170.231.37.0/24 | No route object for it. A route object for 170.231.36.0/22 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 170.231.38.0/24 | No route object for it. A route object for 170.231.36.0/22 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 170.231.39.0/24 | No route object for it. A route object for 170.231.36.0/22 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.152.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.153.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.154.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.155.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.156.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.157.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.158.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.81.159.0/24 | No route object for it. A route object for 200.81.152.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.185.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.186.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.187.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.188.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.189.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.190.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: none | 200.110.191.0/24 | No route object for it. A route object for 200.110.184.0/21 with origin AS27851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27851 in the RIR database for the space. |
| Route object: RIR | 200.110.184.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS27851 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.