Network · data from 2026-11-12

AS393894 MSR-CABLE-TV - MSR PRIVATE CABLE TV

Registry name: MSR-CABLE-TV - MSR PRIVATE CABLE TV, MF · not in PeeringDB

9IPv4 routes 88.9% RPKI valid · 88.9% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS393894, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS393894, 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.139.192.0/24	No ROA	Other IRR onlyRADB	672 100%	67
45.145.145.0/24	Valid	Nonecovered by 45.145.144.0/22	671 100%	67
45.15.196.0/22	Valid	Other IRR onlyRADB	672 100%	67
45.80.100.0/22	Valid	Other IRR onlyRADB	672 100%	67
45.15.196.0/23	Valid	RIR databaseRIPE	672 100%	67
45.15.198.0/23	Valid	RIR databaseRIPE	672 100%	67
45.80.100.0/23	Valid	RIR databaseRIPE	672 100%	67
45.80.102.0/23	Valid	RIR databaseRIPE	672 100%	67
45.145.144.0/22	Valid	RIR databaseRADB, RIPE	672 100%	67

AS-SET

AS393894 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 5 are in fix.csv.

ROA: none1
Route object: none1
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: none	192.139.192.0/24	No ROA covers it. Add a ROA for AS393894, maxLength 24.	672 of 673
Route object: RIR	192.139.192.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: none	45.145.145.0/24	No route object for it. A route object for 45.145.144.0/22 with origin AS393894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393894 in the RIR database for the space.	671 of 673
Route object: RIR	45.15.196.0/22	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.80.100.0/22	Route object only in RADB. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

192.139.192.0/24

No ROA covers it. Add a ROA for AS393894, maxLength 24.

672 of 673

Route object: RIR

192.139.192.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route object: none

45.145.145.0/24

No route object for it. A route object for 45.145.144.0/22 with origin AS393894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393894 in the RIR database for the space.

671 of 673

Route object: RIR

45.15.196.0/22

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route object: RIR

45.80.100.0/22

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route objects not announced

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