bgpreport

Network · data from 2026-11-12

AS52349 Young S.A.

Registry name: AS52349 - Young S.A., AR · PeeringDB

22IPv4 routes 90.9% RPKI valid · 9.1% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
0No ROA 20 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS52349, seen from no peer

Announced routes

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

45.236.40.0/24 Invalid: origin None 1 0%low visibility 2
45.236.43.0/24 Invalid: origin None 1 0%low visibility 2
170.246.244.0/24 Valid Nonecovered by 170.246.244.0/22 672 100% 66
170.246.245.0/24 Valid Nonecovered by 170.246.244.0/22 672 100% 66
186.148.249.0/24 Valid Nonecovered by 186.148.248.0/21 672 100% 66
186.148.254.0/24 Valid Nonecovered by 186.148.248.0/21 672 100% 66
138.0.8.0/24 Valid Nonecovered by 138.0.8.0/22 671 100% 67
138.0.9.0/24 Valid Nonecovered by 138.0.8.0/22 671 100% 67
186.148.251.0/24 Valid Nonecovered by 186.148.248.0/21 671 100% 67
186.148.252.0/23 Valid Nonecovered by 186.148.248.0/21 671 100% 67
186.148.252.0/24 Valid Nonecovered by 186.148.248.0/21 671 100% 67
186.148.253.0/24 Valid Nonecovered by 186.148.248.0/21 671 100% 67
186.148.255.0/24 Valid Nonecovered by 186.148.248.0/21 671 100% 67
138.0.11.0/24 Valid Nonecovered by 138.0.8.0/22 670 100% 67
170.246.246.0/24 Valid Nonecovered by 170.246.244.0/22 670 100% 67
170.246.247.0/24 Valid Nonecovered by 170.246.244.0/22 670 100% 67
186.148.248.0/24 Valid Nonecovered by 186.148.248.0/21 670 100% 67
186.148.250.0/24 Valid Nonecovered by 186.148.248.0/21 670 100% 67
138.0.10.0/23 Valid Nonecovered by 138.0.8.0/22 2 0%low visibility 2
138.0.10.0/24 Valid Nonecovered by 138.0.8.0/22 2 0%low visibility 2
186.148.248.0/21 Valid RIR databaseLACNIC 106 16% 41
170.246.244.0/22 Valid RIR databaseLACNIC 2 0%low visibility 2

AS-SET

AS52349'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 24 are in fix.csv.

  • ROA: origin2
  • Route object: none20
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin45.236.40.0/24ROAs covering it name AS266813, not AS52349. If AS52349 should announce it, add a ROA for AS52349.1 of 673
Route object: none45.236.40.0/24No route object for it. Add a route object with origin AS52349 in the RIR database for the space.1 of 673
ROA: origin45.236.43.0/24ROAs covering it name AS266813, not AS52349. If AS52349 should announce it, add a ROA for AS52349.1 of 673
Route object: none45.236.43.0/24No route object for it. Add a route object with origin AS52349 in the RIR database for the space.1 of 673
Route object: none170.246.244.0/24No route object for it. A route object for 170.246.244.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.672 of 673
Route object: none170.246.245.0/24No route object for it. A route object for 170.246.244.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.672 of 673
Route object: none186.148.249.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.672 of 673
Route object: none186.148.254.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.672 of 673
Route object: none138.0.8.0/24No route object for it. A route object for 138.0.8.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none138.0.9.0/24No route object for it. A route object for 138.0.8.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none186.148.251.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none186.148.252.0/23No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none186.148.252.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none186.148.253.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none186.148.255.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.671 of 673
Route object: none138.0.11.0/24No route object for it. A route object for 138.0.8.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.670 of 673
Route object: none170.246.246.0/24No route object for it. A route object for 170.246.244.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.670 of 673
Route object: none170.246.247.0/24No route object for it. A route object for 170.246.244.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.670 of 673
Route object: none186.148.248.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.670 of 673
Route object: none186.148.250.0/24No route object for it. A route object for 186.148.248.0/21 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.670 of 673
Route object: none138.0.10.0/23No route object for it. A route object for 138.0.8.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.2 of 673
Route object: none138.0.10.0/24No route object for it. A route object for 138.0.8.0/22 with origin AS52349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52349 in the RIR database for the space.2 of 673

Route objects not announced

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

138.0.8.0/22LACNICValid
2800:9c0::/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.