bgpreport

Network · data from 2026-11-12

AS27754 Cooperativa Batan de Obras y Serv. Publicos

Registry name: AS27754 - Cooperativa Batan de Obras y Serv. Publicos Ltda, AR · PeeringDB

33IPv4 routes 100.0% RPKI valid · 39.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 20 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS27754, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27754, 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.

181.41.253.0/24 Valid Nonecovered by 181.41.248.0/21 673 100% 67
181.41.254.0/24 Valid Nonecovered by 181.41.248.0/21 673 100% 67
181.41.255.0/24 Valid Nonecovered by 181.41.248.0/21 673 100% 67
186.38.90.0/24 Valid Nonecovered by 186.38.90.0/23 673 100% 67
200.80.224.0/24 Valid None 672 100% 67
200.80.244.0/24 Valid None 672 100% 67
181.41.224.0/24 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.225.0/24 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.226.0/23 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.228.0/23 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.230.0/24 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.231.0/24 Valid Nonecovered by 181.41.224.0/21 671 100% 67
181.41.232.0/24 Valid Nonecovered by 181.41.232.0/21 671 100% 67
181.41.242.0/24 Valid Nonecovered by 181.41.240.0/21 671 100% 67
181.41.244.0/22 Valid Nonecovered by 181.41.240.0/21 671 100% 67
181.41.249.0/24 Valid Nonecovered by 181.41.248.0/21 671 100% 67
181.41.250.0/24 Valid Nonecovered by 181.41.248.0/21 671 100% 67
181.41.251.0/24 Valid Nonecovered by 181.41.248.0/21 671 100% 67
181.41.252.0/24 Valid Nonecovered by 181.41.248.0/21 671 100% 67
190.3.22.0/24 Valid None 670 100% 67
200.61.46.0/24 Valid Other IRR onlyRADB 672 100% 67
181.41.224.0/21 Valid Other IRR onlyRADB 671 100% 67
181.41.240.0/21 Valid Other IRR onlyRADB 671 100% 67
181.41.248.0/21 Valid Other IRR onlyRADB 671 100% 67
186.38.91.0/24 Valid Other IRR onlyRADB 671 100% 67
181.41.232.0/21 Valid Other IRR onlyRADB 670 100% 67
186.56.39.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
186.56.50.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
201.251.249.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
186.38.89.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
186.38.92.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
186.38.108.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
186.38.110.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS27754: AS27754:AS-ECOLAN. 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 (AS27754 isn't in the set, or no route object for AS27754 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.

NameDatabaseASNsSets Route objectsAS27754 in itNot covered
AS27754:AS-ECOLAN LACNIC 7146 Yes 3

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 31 are in fix.csv.

  • Route object: none20
  • Route object: RIR6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none181.41.253.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.673 of 673
Route object: none181.41.254.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.673 of 673
Route object: none181.41.255.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.673 of 673
Route object: none186.38.90.0/24No route object for it. A route object for 186.38.90.0/23 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.673 of 673
Route object: none200.80.224.0/24No route object for it. Add a route object with origin AS27754 in the RIR database for the space.672 of 673
Route object: none200.80.244.0/24No route object for it. Add a route object with origin AS27754 in the RIR database for the space.672 of 673
Route object: none181.41.224.0/24No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.225.0/24No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.226.0/23No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.228.0/23No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.230.0/24No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.231.0/24No route object for it. A route object for 181.41.224.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.232.0/24No route object for it. A route object for 181.41.232.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.242.0/24No route object for it. A route object for 181.41.240.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.244.0/22No route object for it. A route object for 181.41.240.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.249.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.250.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.251.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none181.41.252.0/24No route object for it. A route object for 181.41.248.0/21 with origin AS27754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27754 in the RIR database for the space.671 of 673
Route object: none190.3.22.0/24No route object for it. Add a route object with origin AS27754 in the RIR database for the space.670 of 673
Route object: RIR200.61.46.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR181.41.224.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR181.41.240.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR181.41.248.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.38.91.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR181.41.232.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS27754 whose prefix no peer sees AS27754 announce. Many are kept on purpose (backup routes, space announced only in some places).

181.41.224.0/19LACNICValid
186.38.90.0/23LACNICValid
200.47.81.0/24LACNICValid
201.251.73.0/24LACNICValid
2803:ca00::/32LACNICValid

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.