Network · data from 2026-11-12

AS273035 AS273035 - CORPORACION LORIATELECOM S.A.S.

Registry name: AS273035 - CORPORACION LORIATELECOM S.A.S., EC · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object

2IPv6 routes 0.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 3 with no route object for this origin

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

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

Announced routes

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


2803:2b90::/40	No ROA	Nonecovered by 2803:2b90::/32	636 100%	67
2803:2b90::/32	No ROA	Other IRR onlyRADB	636 100%	67
168.232.100.0/24	Valid	Nonecovered by 168.232.100.0/23	668 99%	67
168.232.101.0/24	Valid	Nonecovered by 168.232.100.0/23	667 99%	67
168.232.100.0/23	Valid	RIR databaseLACNIC	666 99%	67

AS-SET

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

ROA: none2
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2803:2b90::/40	No ROA covers it. Add a ROA for AS273035, maxLength 40.	636 of 636
Route object: none	2803:2b90::/40	No route object for it. A route object for 2803:2b90::/32 with origin AS273035 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273035 in the RIR database for the space.	636 of 636
ROA: none	2803:2b90::/32	No ROA covers it. Add a ROA for AS273035, maxLength 32.	636 of 636
Route object: RIR	2803:2b90::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636
Route object: none	168.232.100.0/24	No route object for it. A route object for 168.232.100.0/23 with origin AS273035 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273035 in the RIR database for the space.	668 of 673
Route object: none	168.232.101.0/24	No route object for it. A route object for 168.232.100.0/23 with origin AS273035 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273035 in the RIR database for the space.	667 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

2803:2b90::/40

No ROA covers it. Add a ROA for AS273035, maxLength 40.

636 of 636

Route object: none

2803:2b90::/40

No route object for it. A route object for 2803:2b90::/32 with origin AS273035 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273035 in the RIR database for the space.

636 of 636

ROA: none

2803:2b90::/32

No ROA covers it. Add a ROA for AS273035, maxLength 32.

636 of 636

Route object: RIR

2803:2b90::/32

Route object only in RADB. Add it in the RIR database for the space.

636 of 636

Route object: none

168.232.100.0/24

No route object for it. A route object for 168.232.100.0/23 with origin AS273035 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273035 in the RIR database for the space.

668 of 673

Route object: none

168.232.101.0/24

667 of 673

Route objects not announced

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