Network · data from 2026-11-12

AS262148 AS262148 - Universidad APEC

Registry name: AS262148 - Universidad APEC, DO · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


2801:0:80::/48	No ROA	Other IRR onlyRADB	635 100%	67
200.14.79.0/24	Valid	Other IRR onlyNTTCOM	672 100%	67

AS-SET

AS262148 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.

ROA: none1
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	2801:0:80::/48	No ROA covers it. Add a ROA for AS262148, maxLength 48.	635 of 636
Route object: RIR	2801:0:80::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	200.14.79.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

2801:0:80::/48

No ROA covers it. Add a ROA for AS262148, maxLength 48.

635 of 636

Route object: RIR

2801:0:80::/48

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

635 of 636

Route object: RIR

200.14.79.0/24

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

672 of 673

Route objects not announced

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