bgpreport

Network · data from 2026-11-12

AS271843 AS271843 - LARA INGENIERIA EN TECNOLOGIA Y TELECOMUNICACIONES LIMITADA (SOLUCIONES INTERLAN)

Registry name: AS271843 - LARA INGENIERIA EN TECNOLOGIA Y TELECOMUNICACIONES LIMITADA (SOLUCIONES INTERLAN), CL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271843, 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.
45.162.132.0/23 Valid RIR databaseLACNIC, RADB 671 100% 67
45.162.134.0/24 Valid RIR databaseLACNIC 671 100% 67
45.162.132.0/24 Valid RIR databaseLACNIC 110 16% 41
45.162.133.0/24 Valid RIR databaseLACNIC 110 16% 41

AS-SET

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

  • Route object: not announced3

Route objects not announced

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

45.162.132.0/22ALTDB, RADBNo ROA
45.162.134.0/23RADBNo ROA
2803:f810::/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.