bgpreport

Network · data from 2026-11-12

AS50761 LUX-TV-AS LUX-TV Ltd.

Registry name: LUX-TV-AS LUX-TV Ltd., RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50761, 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.
109.197.255.0/24 No ROA Nonecovered by 109.197.248.0/21 672 100% 66
91.215.20.0/22 No ROA RIR databaseRIPE 673 100% 66
109.197.248.0/21 No ROA RIR databaseRIPE 673 100% 66
109.197.251.0/24 No ROA RIR databaseRIPE 673 100% 66
109.197.253.0/24 No ROA RIR databaseRIPE 673 100% 66
109.197.254.0/24 No ROA RIR databaseRIPE 673 100% 66
91.215.20.0/24 No ROA RIR databaseRIPE 672 100% 66
91.215.21.0/24 No ROA RIR databaseRIPE 672 100% 66
91.215.22.0/24 No ROA RIR databaseRIPE 672 100% 66
91.215.23.0/24 No ROA RIR databaseRIPE 672 100% 66
109.197.248.0/24 No ROA RIR databaseRIPE 672 100% 66
109.197.249.0/24 No ROA RIR databaseRIPE 672 100% 66
109.197.250.0/24 No ROA RIR databaseRIPE 672 100% 66
109.197.252.0/24 No ROA RIR databaseRIPE 672 100% 66

AS-SET

AS50761 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 15 are in fix.csv.

  • ROA: none14
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none109.197.255.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
Route object: none109.197.255.0/24No route object for it. A route object for 109.197.248.0/21 with origin AS50761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50761 in the RIR database for the space.672 of 673
ROA: none91.215.20.0/22No ROA covers it. Add a ROA for AS50761, maxLength 22.673 of 673
ROA: none109.197.248.0/21No ROA covers it. Add a ROA for AS50761, maxLength 21.673 of 673
ROA: none109.197.251.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.673 of 673
ROA: none109.197.253.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.673 of 673
ROA: none109.197.254.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.673 of 673
ROA: none91.215.20.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none91.215.21.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none91.215.22.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none91.215.23.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none109.197.248.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none109.197.249.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none109.197.250.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673
ROA: none109.197.252.0/24No ROA covers it. Add a ROA for AS50761, maxLength 24.672 of 673

Route objects not announced

Every route object with origin AS50761 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.