bgpreport

Network · data from 2026-11-12

AS269802 AS269802 - COOPERATIVA DE SERVICIOS TELEFONICOS Y OTROS SERVICIOS PUBLICOS DE CATRIEL LTDA

Registry name: AS269802 - COOPERATIVA DE SERVICIOS TELEFONICOS Y OTROS SERVICIOS PUBLICOS DE CATRIEL LTDA, AR · not in PeeringDB

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

Announced routes

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

186.38.100.0/24 Invalid: origin None 1 0%low visibility 2
45.186.129.0/24 Valid Nonecovered by 45.186.128.0/22 672 100% 66
45.186.131.0/24 Valid Nonecovered by 45.186.128.0/22 672 100% 66
45.186.128.0/24 Valid Nonecovered by 45.186.128.0/22 671 100% 66
45.186.130.0/24 Valid Nonecovered by 45.186.128.0/22 671 100% 66
45.186.128.0/22 Valid RIR databaseLACNIC 672 100% 66

AS-SET

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

  • ROA: origin1
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin186.38.100.0/24ROAs covering it name AS22927, not AS269802. If AS269802 should announce it, add a ROA for AS269802.1 of 673
Route object: none186.38.100.0/24No route object for it. Add a route object with origin AS269802 in the RIR database for the space.1 of 673
Route object: none45.186.129.0/24No route object for it. A route object for 45.186.128.0/22 with origin AS269802 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269802 in the RIR database for the space.672 of 673
Route object: none45.186.131.0/24No route object for it. A route object for 45.186.128.0/22 with origin AS269802 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269802 in the RIR database for the space.672 of 673
Route object: none45.186.128.0/24No route object for it. A route object for 45.186.128.0/22 with origin AS269802 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269802 in the RIR database for the space.671 of 673
Route object: none45.186.130.0/24No route object for it. A route object for 45.186.128.0/22 with origin AS269802 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269802 in the RIR database for the space.671 of 673

Route objects not announced

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

2803:2b60::/32LACNICValid

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.