bgpreport

Network · data from 2026-11-12

AS264652 AS264652 - COOPERATIVA TELEFONICA VILLA ELOISA

Registry name: AS264652 - COOPERATIVA TELEFONICA VILLA ELOISA, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264652, 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.
143.255.36.0/23 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.36.0/24 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.37.0/24 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.38.0/23 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.38.0/24 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.39.0/24 Valid Nonecovered by 143.255.36.0/22 12 2%low visibility 7
143.255.36.0/22 Valid RIR databaseLACNIC 662 98% 67

AS-SET

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

  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none143.255.36.0/23No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673
Route object: none143.255.36.0/24No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673
Route object: none143.255.37.0/24No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673
Route object: none143.255.38.0/23No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673
Route object: none143.255.38.0/24No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673
Route object: none143.255.39.0/24No route object for it. A route object for 143.255.36.0/22 with origin AS264652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264652 in the RIR database for the space.12 of 673

Route objects not announced

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

2803:7940::/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.