bgpreport

Network · data from 2026-11-12

AS263777 COOPERATIVA TELEFONICA Y OSPA DE TOSTADO

Registry name: AS263777 - COOPERATIVA TELEFONICA Y OSPA DE TOSTADO LDA., AR · PeeringDB

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

Announced routes

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

138.204.6.0/24 Valid Nonecovered by 138.204.4.0/22 672 100% 66
138.204.7.0/24 Valid Nonecovered by 138.204.4.0/22 672 100% 66
168.227.254.0/24 Valid Nonecovered by 168.227.252.0/22 672 100% 66
168.227.255.0/24 Valid Nonecovered by 168.227.252.0/22 672 100% 66
170.239.33.0/24 Valid Nonecovered by 170.239.32.0/22 672 100% 66
170.239.34.0/24 Valid Nonecovered by 170.239.32.0/22 672 100% 66
170.239.35.0/24 Valid Nonecovered by 170.239.32.0/22 672 100% 66
190.227.188.0/23 Valid Nonecovered by 190.227.188.0/22 671 100% 66
190.228.44.0/24 Valid Nonecovered by 190.228.44.0/23 671 100% 66
190.228.45.0/24 Valid Nonecovered by 190.228.44.0/23 671 100% 66
138.204.4.0/23 Valid Nonecovered by 138.204.4.0/22 670 100% 67
170.239.32.0/24 Valid Other IRR onlyRADB 672 100% 66
168.227.252.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
170.239.32.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
190.122.94.0/24 Valid RIR databaseALTDB, LACNIC 671 100% 66
190.227.188.0/22 Valid RIR databaseLACNIC 671 100% 66
190.228.44.0/23 Valid RIR databaseLACNIC 671 100% 66
138.204.4.0/22 Valid RIR databaseLACNIC, RADB 670 100% 67

AS-SET

AS263777'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 17 are in fix.csv.

  • Route object: none11
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none138.204.6.0/24No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none138.204.7.0/24No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none168.227.254.0/24No route object for it. A route object for 168.227.252.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none168.227.255.0/24No route object for it. A route object for 168.227.252.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none170.239.33.0/24No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none170.239.34.0/24No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none170.239.35.0/24No route object for it. A route object for 170.239.32.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.672 of 673
Route object: none190.227.188.0/23No route object for it. A route object for 190.227.188.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.671 of 673
Route object: none190.228.44.0/24No route object for it. A route object for 190.228.44.0/23 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.671 of 673
Route object: none190.228.45.0/24No route object for it. A route object for 190.228.44.0/23 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.671 of 673
Route object: none138.204.4.0/23No route object for it. A route object for 138.204.4.0/22 with origin AS263777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263777 in the RIR database for the space.670 of 673
Route object: RIR170.239.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

138.204.4.0/24RADBValid
168.227.252.0/24RADBValid
2802:2240::/32RADBNo ROA
2803:2240::/32LACNIC, RADBValid
2803:2240::/48RADBValid

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.