bgpreport

Network · data from 2026-11-12

AS262222 Oficina Provincial de Tecnologias de la Información (O.P.T.I.C.)

Registry name: AS262222 - Oficina Provincial de Tecnologias de la Informacion (O.P.T.I.C.), AR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS262222, seen from no peer

Announced routes

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

190.185.100.0/23 Valid None 669 99% 66
190.185.102.0/24 Valid None 669 99% 66
190.185.103.0/24 Valid None 669 99% 66

AS-SET

AS262222's PeeringDB record names no 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: none3
ChangePrefix or setDetailFull-table peers
Route object: none190.185.100.0/23No route object for it. Add a route object with origin AS262222 in the RIR database for the space.669 of 673
Route object: none190.185.102.0/24No route object for it. Add a route object with origin AS262222 in the RIR database for the space.669 of 673
Route object: none190.185.103.0/24No route object for it. Add a route object with origin AS262222 in the RIR database for the space.669 of 673

Route objects not announced

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