bgpreport

Network · data from 2026-11-12

AS52369 NEOPHONE ARGENTINA

Registry name: AS52369 - NEOPHONE ARGENTINA SRL, AR · PeeringDB

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

Announced routes

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

179.42.176.0/20 Valid RIR databaseLACNIC, RADB 670 100% 66
179.42.184.0/22 Valid RIR databaseLACNIC 670 100% 66
179.42.176.0/23 Valid RIR databaseLACNIC 669 99% 66
179.42.178.0/24 Valid RIR databaseLACNIC 669 99% 66
179.42.179.0/24 Valid RIR databaseLACNIC 669 99% 66
179.42.180.0/22 Valid RIR databaseLACNIC 669 99% 66
179.42.184.0/23 Valid RIR databaseLACNIC 669 99% 66
179.42.189.0/24 Valid RIR databaseLACNIC 669 99% 66
190.110.112.0/21 Valid RIR databaseLACNIC, RADB 669 99% 66
190.110.116.0/24 Valid RIR databaseLACNIC 669 99% 66
190.110.117.0/24 Valid RIR databaseLACNIC 669 99% 66
190.110.118.0/24 Valid RIR databaseLACNIC 669 99% 66
190.110.119.0/24 Valid RIR databaseLACNIC 669 99% 66
190.184.224.0/20 Valid RIR databaseLACNIC, RADB 669 99% 66
190.110.112.0/24 Valid RIR databaseLACNIC 668 99% 66
190.110.113.0/24 Valid RIR databaseLACNIC 668 99% 66
190.110.114.0/24 Valid RIR databaseLACNIC 668 99% 66
190.110.115.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.224.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.225.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.226.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.227.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.228.0/22 Valid RIR databaseLACNIC 668 99% 66
190.184.230.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.231.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.233.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.236.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.237.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.238.0/24 Valid RIR databaseLACNIC 668 99% 66
190.184.239.0/24 Valid RIR databaseLACNIC 668 99% 66

AS-SET

AS52369'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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

179.42.176.0/24LACNICValid
179.42.177.0/24LACNICValid
179.42.180.0/23LACNICValid
179.42.182.0/24LACNICValid
179.42.183.0/24LACNICValid
179.42.184.0/24LACNICValid
179.42.185.0/24LACNICValid
179.42.186.0/24LACNICValid
179.42.187.0/24LACNICValid
179.42.188.0/24LACNICValid
179.42.190.0/23LACNICValid
190.184.228.0/24LACNICValid
190.184.229.0/24LACNICValid
190.184.234.0/24LACNICValid
190.184.235.0/24LACNICValid
2800:c50::/32LACNIC, RADBValid

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.