Network · data from 2026-11-12

AS274270 AS274270 - EQUIPOS-SERVICIOS DE SEGURIDAD Y COMPUTO ESERSEC S.A.C. - ESERSEC S.A.C.

Registry name: AS274270 - EQUIPOS-SERVICIOS DE SEGURIDAD Y COMPUTO ESERSEC S.A.C. - ESERSEC S.A.C., PE · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object

4IPv6 routes 100.0% RPKI valid · 25.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 4 with no route object for this origin

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

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

Announced routes

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


198.242.63.0/24	No ROA	None	672 100%	67
2803:8030::/40	Valid	Nonecovered by 2803:8030::/32	635 100%	67
2803:8030:200::/40	Valid	Nonecovered by 2803:8030::/32	635 100%	67
2803:8030:100::/40	Valid	Nonecovered by 2803:8030::/32	634 100%	67
2803:8030::/32	Valid	Other IRR onlyRADB	636 100%	69

AS-SET

AS274270 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: none1
Route object: none4
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	198.242.63.0/24	No ROA covers it. Add a ROA for AS274270, maxLength 24.	672 of 673
Route object: none	198.242.63.0/24	No route object for it. Add a route object with origin AS274270 in the RIR database for the space.	672 of 673
Route object: none	2803:8030::/40	No route object for it. A route object for 2803:8030::/32 with origin AS274270 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274270 in the RIR database for the space.	635 of 636
Route object: none	2803:8030:200::/40	No route object for it. A route object for 2803:8030::/32 with origin AS274270 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274270 in the RIR database for the space.	635 of 636
Route object: none	2803:8030:100::/40	No route object for it. A route object for 2803:8030::/32 with origin AS274270 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274270 in the RIR database for the space.	634 of 636
Route object: RIR	2803:8030::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

198.242.63.0/24

No ROA covers it. Add a ROA for AS274270, maxLength 24.

672 of 673

Route object: none

198.242.63.0/24

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

672 of 673

Route object: none

2803:8030::/40

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

635 of 636

Route object: none

2803:8030:200::/40

635 of 636

Route object: none

2803:8030:100::/40

634 of 636

Route object: RIR

2803:8030::/32

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

636 of 636

Route objects not announced

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