bgpreport

Network · data from 2026-11-12

AS265539 AS265539 - LIBERTY NETWORKS SOLUTIONS MEXICO

Registry name: AS265539 - LIBERTY NETWORKS SOLUTIONS MEXICO, MX · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS265539, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265539, 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.
181.191.189.0/24 No ROA Nonecovered by 181.191.188.0/22 671 100% 67
2806:2ee:0:2::/64 No ROA Nonecovered by 2806:2ee::/32 0 0%low visibility 1
2806:2ee:0:3::/64 No ROA Nonecovered by 2806:2ee::/32 0 0%low visibility 1
181.191.188.0/22 No ROA Other IRR onlyRADB 671 100% 67
181.191.188.0/24 No ROA Other IRR onlyRADB 671 100% 67
2806:2ee::/32 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none181.191.189.0/24No ROA covers it. Add a ROA for AS265539, maxLength 24.671 of 673
Route object: none181.191.189.0/24No route object for it. A route object for 181.191.188.0/22 with origin AS265539 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265539 in the RIR database for the space.671 of 673
ROA: none2806:2ee:0:2::/64No ROA covers it. Add a ROA for AS265539, maxLength 64.0 of 636
Route object: none2806:2ee:0:2::/64No route object for it. A route object for 2806:2ee::/32 with origin AS265539 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS265539 in the RIR database for the space.0 of 636
ROA: none2806:2ee:0:3::/64No ROA covers it. Add a ROA for AS265539, maxLength 64.0 of 636
Route object: none2806:2ee:0:3::/64No route object for it. A route object for 2806:2ee::/32 with origin AS265539 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS265539 in the RIR database for the space.0 of 636
ROA: none181.191.188.0/22No ROA covers it. Add a ROA for AS265539, maxLength 22.671 of 673
Route object: RIR181.191.188.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none181.191.188.0/24No ROA covers it. Add a ROA for AS265539, maxLength 24.671 of 673
Route object: RIR181.191.188.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2806:2ee::/32No ROA covers it. Add a ROA for AS265539, maxLength 32.635 of 636
Route object: RIR2806:2ee::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS265539 is announced.

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.