bgpreport

Network · data from 2026-11-12

AS265823 NETROPOLYS S.A.

Registry name: AS265823 - NETROPOLYS S.A., AR · PeeringDB

11IPv4 routes 100.0% RPKI valid · 72.7% 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
2Route objects not announced registered with origin AS265823, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265823, 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.
192.141.92.0/23 Valid Nonecovered by 192.141.92.0/22 670 100% 67
192.141.94.0/23 Valid Nonecovered by 192.141.92.0/22 670 100% 67
132.255.11.0/24 Valid Other origin onlycovered by 132.255.8.0/22 104 15% 41
132.255.8.0/24 Valid Other IRR onlyRADB 104 15% 41
132.255.9.0/24 Valid Other IRR onlyRADB 104 15% 41
132.255.10.0/24 Valid Other IRR onlyRADB 104 15% 41
192.141.92.0/24 Valid Other IRR onlyRADB 104 15% 41
192.141.93.0/24 Valid Other IRR onlyRADB 104 15% 41
192.141.94.0/24 Valid Other IRR onlyRADB 104 15% 41
192.141.95.0/24 Valid Other IRR onlyRADB 104 15% 41
132.255.8.0/22 Valid RIR databaseLACNIC, RADB 671 100% 67

AS-SET

AS265823'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 12 are in fix.csv.

  • Route object: none3
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none192.141.92.0/23No route object for it. A route object for 192.141.92.0/22 with origin AS265823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265823 in the RIR database for the space.670 of 673
Route object: none192.141.94.0/23No route object for it. A route object for 192.141.92.0/22 with origin AS265823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265823 in the RIR database for the space.670 of 673
Route object: none132.255.11.0/24Route objects for it name AS273116. A route object for 132.255.8.0/22 with origin AS265823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265823 in the RIR database for the space.104 of 673
Route object: RIR132.255.8.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR132.255.9.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR132.255.10.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR192.141.92.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR192.141.93.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR192.141.94.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR192.141.95.0/24Route object only in RADB. Add it in the RIR database for the space.104 of 673

Route objects not announced

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

192.141.92.0/22LACNIC, RADBValid
2803:9420::/32RADBNo ROA

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.