bgpreport

Network · data from 2026-11-12

AS48123 STREAM-TV-KALUGA MTS PJSC

Registry name: STREAM-TV-KALUGA MTS PJSC, RU · not in PeeringDB

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

Announced routes

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

85.140.74.0/24 Invalid: origin Nonecovered by 85.140.72.0/22 89 13% 39
93.187.176.0/23 No ROA Nonecovered by 93.187.176.0/22 671 100% 67
93.187.178.0/23 No ROA Nonecovered by 93.187.176.0/22 671 100% 67
193.194.96.0/24 No ROA RIR databaseRIPE 671 100% 67
193.194.97.0/24 No ROA RIR databaseRIPE 671 100% 67
193.194.98.0/24 No ROA RIR databaseRIPE 671 100% 67
193.194.99.0/24 No ROA RIR databaseRIPE 671 100% 67
193.194.100.0/23 No ROA RIR databaseRIPE 671 100% 67
85.140.56.0/24 Valid Nonecovered by 85.140.56.0/22 671 100% 67
85.140.57.0/24 Valid Nonecovered by 85.140.56.0/22 671 100% 67
85.140.58.0/24 Valid Nonecovered by 85.140.56.0/22 671 100% 67
85.140.59.0/24 Valid Nonecovered by 85.140.56.0/22 671 100% 67
85.140.72.0/24 Valid Nonecovered by 85.140.72.0/22 671 100% 67
85.140.73.0/24 Valid Nonecovered by 85.140.72.0/22 671 100% 67
81.195.148.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS48123 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 27 are in fix.csv.

  • ROA: origin1
  • ROA: none7
  • Route object: none9
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin85.140.74.0/24ROAs covering it name AS8359, not AS48123. If AS48123 should announce it, add a ROA for AS48123.89 of 673
Route object: none85.140.74.0/24No route object for it. A route object for 85.140.72.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.89 of 673
ROA: none93.187.176.0/23No ROA covers it. Add a ROA for AS48123, maxLength 23.671 of 673
Route object: none93.187.176.0/23No route object for it. A route object for 93.187.176.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
ROA: none93.187.178.0/23No ROA covers it. Add a ROA for AS48123, maxLength 23.671 of 673
Route object: none93.187.178.0/23No route object for it. A route object for 93.187.176.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
ROA: none193.194.96.0/24No ROA covers it. Add a ROA for AS48123, maxLength 24.671 of 673
ROA: none193.194.97.0/24No ROA covers it. Add a ROA for AS48123, maxLength 24.671 of 673
ROA: none193.194.98.0/24No ROA covers it. Add a ROA for AS48123, maxLength 24.671 of 673
ROA: none193.194.99.0/24No ROA covers it. Add a ROA for AS48123, maxLength 24.671 of 673
ROA: none193.194.100.0/23No ROA covers it. Add a ROA for AS48123, maxLength 23.671 of 673
Route object: none85.140.56.0/24No route object for it. A route object for 85.140.56.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
Route object: none85.140.57.0/24No route object for it. A route object for 85.140.56.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
Route object: none85.140.58.0/24No route object for it. A route object for 85.140.56.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
Route object: none85.140.59.0/24No route object for it. A route object for 85.140.56.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
Route object: none85.140.72.0/24No route object for it. A route object for 85.140.72.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673
Route object: none85.140.73.0/24No route object for it. A route object for 85.140.72.0/22 with origin AS48123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48123 in the RIR database for the space.671 of 673

Route objects not announced

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

85.140.56.0/22RIPEInvalid: origin
85.140.72.0/22RIPEInvalid: origin
93.187.176.0/22RIPENo ROA
93.187.176.0/24RIPENo ROA
93.187.177.0/24RIPENo ROA
93.187.178.0/24RIPENo ROA
93.187.179.0/24RIPENo ROA
193.194.96.0/22RIPENo ROA
193.194.100.0/24RIPENo ROA
193.194.101.0/24RIPENo ROA

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.