bgpreport

Network · data from 2026-11-12

AS269823 AS269823 - COOPERATIVA AGUA POTABLE, VIVIENDAS Y OTROS SERVICIOS PUBLICOS DE ORIENTE LTDA

Registry name: AS269823 - COOPERATIVA AGUA POTABLE, VIVIENDAS Y OTROS SERVICIOS PUBLICOS DE ORIENTE LTDA, AR · not in PeeringDB

6IPv4 routes 16.7% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS269823, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269823, 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.
45.184.107.0/24 No ROA Nonecovered by 45.184.104.0/22 666 99% 67
45.184.104.0/24 No ROA Nonecovered by 45.184.104.0/22 102 15% 39
45.184.105.0/24 No ROA Nonecovered by 45.184.104.0/22 102 15% 39
45.184.106.0/24 No ROA Nonecovered by 45.184.104.0/22 102 15% 39
45.184.104.0/22 No ROA Other IRR onlyRADB 672 100% 67
201.251.239.0/24 Valid RIR databaseLACNIC 671 100% 67

AS-SET

AS269823 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.184.107.0/24No ROA covers it. Add a ROA for AS269823, maxLength 24.666 of 673
Route object: none45.184.107.0/24No route object for it. A route object for 45.184.104.0/22 with origin AS269823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269823 in the RIR database for the space.666 of 673
ROA: none45.184.104.0/24No ROA covers it. Add a ROA for AS269823, maxLength 24.102 of 673
Route object: none45.184.104.0/24No route object for it. A route object for 45.184.104.0/22 with origin AS269823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269823 in the RIR database for the space.102 of 673
ROA: none45.184.105.0/24No ROA covers it. Add a ROA for AS269823, maxLength 24.102 of 673
Route object: none45.184.105.0/24No route object for it. A route object for 45.184.104.0/22 with origin AS269823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269823 in the RIR database for the space.102 of 673
ROA: none45.184.106.0/24No ROA covers it. Add a ROA for AS269823, maxLength 24.102 of 673
Route object: none45.184.106.0/24No route object for it. A route object for 45.184.104.0/22 with origin AS269823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269823 in the RIR database for the space.102 of 673
ROA: none45.184.104.0/22No ROA covers it. Add a ROA for AS269823, maxLength 22.672 of 673
Route object: RIR45.184.104.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS269823 whose prefix no peer sees AS269823 announce. Many are kept on purpose (backup routes, space announced only in some places).

201.251.7.128/26LACNICValid

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.