Network · data from 2026-11-12

AS274989 AS274989 - NEXO TELECOMUNICACIONES SPA

Registry name: AS274989 - NEXO TELECOMUNICACIONES SPA, CL · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 50.0% with a route object

1IPv6 routes 100.0% RPKI valid · 0.0% with a route object

2RPKI invalid 0 origin · 2 maxLength

0No ROA 3 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS274989, seen from no peer

Announced routes

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


192.48.178.0/24	Invalid: maxLength	Other origin onlycovered by 192.48.178.0/23	3 0%low visibility	3
192.48.179.0/24	Invalid: maxLength	Other origin onlycovered by 192.48.178.0/23	3 0%low visibility	3
2803:5d30::/32	Valid	None	635 100%	67
192.48.178.0/23	Valid	RIR databaseARIN, RADB	673 100%	66
200.229.22.0/24	Valid	RIR databaseARIN, RADB	672 100%	66

192.48.178.0/24

Invalid: maxLength

Other origin onlycovered by 192.48.178.0/23

3 0%low visibility

192.48.179.0/24

Invalid: maxLength

Other origin onlycovered by 192.48.178.0/23

3 0%low visibility

2803:5d30::/32

Valid

None

635 100%

192.48.178.0/23

Valid

RIR databaseARIN, RADB

673 100%

200.229.22.0/24

Valid

RIR databaseARIN, RADB

672 100%

AS-SET

AS274989 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: maxLength2
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	192.48.178.0/24	ROA 192.48.178.0/23 AS274989 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 192.48.178.0/24.	3 of 673
Route object: none	192.48.178.0/24	Route objects for it name AS834. A route object for 192.48.178.0/23 with origin AS274989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274989 in the RIR database for the space.	3 of 673
ROA: maxLength	192.48.179.0/24	ROA 192.48.178.0/23 AS274989 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 192.48.179.0/24.	3 of 673
Route object: none	192.48.179.0/24	Route objects for it name AS834. A route object for 192.48.178.0/23 with origin AS274989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274989 in the RIR database for the space.	3 of 673
Route object: none	2803:5d30::/32	No route object for it. Add a route object with origin AS274989 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

192.48.178.0/24

ROA 192.48.178.0/23 AS274989 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 192.48.178.0/24.

3 of 673

Route object: none

192.48.178.0/24

Route objects for it name AS834. A route object for 192.48.178.0/23 with origin AS274989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274989 in the RIR database for the space.

3 of 673

ROA: maxLength

192.48.179.0/24

ROA 192.48.178.0/23 AS274989 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 192.48.179.0/24.

3 of 673

Route object: none

192.48.179.0/24

3 of 673

Route object: none

2803:5d30::/32

No route object for it. Add a route object with origin AS274989 in the RIR database for the space.

635 of 636

Route objects not announced

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