bgpreport

Network · data from 2026-11-12

AS27845 Empresa de Recursos Tecnologicos

Registry name: AS27845 - Empresa de Recursos Tecnologicos S.A E.S.P, CO · PeeringDB

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

Announced routes

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

190.97.204.0/24 Valid Nonecovered by 190.97.204.0/23 671 100% 67
190.97.205.0/24 Valid Nonecovered by 190.97.204.0/23 670 100% 67
190.6.180.0/23 Valid Nonecovered by 190.6.176.0/20 668 99% 67
190.6.184.0/21 Valid Nonecovered by 190.6.176.0/20 668 99% 67
190.6.160.0/24 Valid Other IRR onlyRADB 671 100% 67
190.6.162.0/24 Valid Other IRR onlyRADB 671 100% 67
190.6.170.0/24 Valid Other IRR onlyRADB 671 100% 67
190.6.174.0/24 Valid Other IRR onlyRADB 671 100% 67
190.6.166.0/24 Valid Other IRR onlyRADB 670 100% 67
190.6.179.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.80.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.81.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.82.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.83.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.95.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.195.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.201.0/24 Valid Other IRR onlyRADB 670 100% 67
190.97.202.0/24 Valid Other IRR onlyRADB 670 100% 67
190.6.167.0/24 Valid Other IRR onlyRADB 669 99% 67
190.6.172.0/24 Valid Other IRR onlyRADB 669 99% 67
190.6.176.0/20 Valid RIR databaseLACNIC, RADB 671 100% 67
190.97.196.0/22 Valid RIR databaseLACNIC 671 100% 67
190.97.206.0/23 Valid RIR databaseLACNIC 671 100% 67
190.97.208.0/20 Valid RIR databaseLACNIC 671 100% 67
190.6.164.0/23 Valid RIR databaseLACNIC 670 100% 67
190.6.168.0/23 Valid RIR databaseLACNIC 670 100% 67
190.97.64.0/22 Valid RIR databaseLACNIC 670 100% 67
190.97.72.0/21 Valid RIR databaseLACNIC 670 100% 67
190.97.84.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
190.97.86.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
190.97.88.0/22 Valid RIR databaseLACNIC 670 100% 67
2800:9f0::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

AS27845'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 64 are in fix.csv.

  • Route object: none4
  • Route object: RIR16
  • Route object: not announced44
ChangePrefix or setDetailFull-table peers
Route object: none190.97.204.0/24No route object for it. A route object for 190.97.204.0/23 with origin AS27845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27845 in the RIR database for the space.671 of 673
Route object: none190.97.205.0/24No route object for it. A route object for 190.97.204.0/23 with origin AS27845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27845 in the RIR database for the space.670 of 673
Route object: none190.6.180.0/23No route object for it. A route object for 190.6.176.0/20 with origin AS27845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27845 in the RIR database for the space.668 of 673
Route object: none190.6.184.0/21No route object for it. A route object for 190.6.176.0/20 with origin AS27845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27845 in the RIR database for the space.668 of 673
Route object: RIR190.6.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.6.162.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.6.170.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.6.174.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.6.166.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.6.179.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.80.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.81.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.82.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.83.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.95.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.195.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.201.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.97.202.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.6.167.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR190.6.172.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

190.6.160.0/22LACNICValid
190.6.161.0/24RADBValid
190.6.163.0/24RADBValid
190.6.166.0/23LACNICValid
190.6.170.0/23LACNICValid
190.6.171.0/24RADBValid
190.6.172.0/22LACNICValid
190.6.173.0/24RADBValid
190.6.175.0/24RADBValid
190.6.176.0/24RADBValid
190.6.177.0/24RADBValid
190.6.178.0/24RADBValid
190.6.180.0/24RADBValid
190.6.181.0/24RADBValid
190.6.182.0/24RADBValid
190.6.183.0/24RADBValid
190.6.184.0/24RADBValid
190.6.185.0/24RADBValid
190.6.186.0/24RADBValid
190.6.187.0/24RADBValid
190.6.188.0/24RADBValid
190.6.189.0/24RADBValid
190.6.190.0/24RADBValid
190.6.191.0/24RADBValid
190.97.68.0/23LACNICValid
190.97.70.0/23LACNICValid
190.97.70.0/24RADBValid
190.97.71.0/24RADBValid
190.97.80.0/22LACNICValid
190.97.88.0/24RADBValid
190.97.89.0/24RADBValid
190.97.90.0/24LACNIC, RADBValid
190.97.91.0/24RADBValid
190.97.92.0/24LACNIC, RADBValid
190.97.94.0/23LACNICValid
190.97.94.0/24RADBValid
190.97.192.0/22LACNICValid
190.97.194.0/24RADBValid
190.97.200.0/22LACNICValid
190.97.200.0/24RADBValid
190.97.203.0/24RADBValid
190.97.204.0/23LACNICValid
201.234.66.0/24RADBNo ROA
201.234.67.0/24RADBNo ROA

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.