bgpreport

Network · data from 2026-11-12

AS272113 AS272113 - COOPERATIVA ELECTRICA Y OTROS SERVICIOS PUBLICOS DE FERRE LIMITADA

Registry name: AS272113 - COOPERATIVA ELECTRICA Y OTROS SERVICIOS PUBLICOS DE FERRE LIMITADA, AR · not in PeeringDB

8IPv4 routes 87.5% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 4 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS272113, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272113, 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.
186.56.107.0/24 Invalid: origin None 1 0%low visibility 2
179.63.102.0/24 Valid Nonecovered by 179.63.100.0/22 671 100% 66
179.63.100.0/24 Valid Nonecovered by 179.63.100.0/22 669 99% 67
179.63.101.0/24 Valid Nonecovered by 179.63.100.0/22 26 4%low visibility 13
179.63.100.0/22 Valid RIR databaseLACNIC 672 100% 66
201.254.230.0/24 Valid RIR databaseLACNIC 672 100% 66
186.56.60.0/24 Valid RIR databaseLACNIC 666 99% 67
201.251.242.0/24 Valid RIR databaseLACNIC 666 99% 67
2803:5f10::/32 Valid RIR databaseLACNIC 3 0%low visibility 3

AS-SET

AS272113 isn't in PeeringDB, where networks name their 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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin186.56.107.0/24ROAs covering it name AS22927, not AS272113. If AS272113 should announce it, add a ROA for AS272113.1 of 673
Route object: none186.56.107.0/24No route object for it. Add a route object with origin AS272113 in the RIR database for the space.1 of 673
Route object: none179.63.102.0/24No route object for it. A route object for 179.63.100.0/22 with origin AS272113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272113 in the RIR database for the space.671 of 673
Route object: none179.63.100.0/24No route object for it. A route object for 179.63.100.0/22 with origin AS272113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272113 in the RIR database for the space.669 of 673
Route object: none179.63.101.0/24No route object for it. A route object for 179.63.100.0/22 with origin AS272113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272113 in the RIR database for the space.26 of 673

Route objects not announced

Every route object with origin AS272113 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.