bgpreport

Network · data from 2026-11-12

AS39493 RU-KSTV CJSC Kolomna-Sviaz TV

Registry name: RU-KSTV CJSC Kolomna-Sviaz TV, RU · not in PeeringDB

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

Announced routes

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

5.42.96.0/19 Invalid: origin None 63 9%low visibility 32
217.196.106.0/24 No ROA None 671 100% 67
5.42.0.0/18 No ROA RIR databaseRIPE 673 100% 67
78.25.128.0/19 No ROA RIR databaseRIPE 672 100% 67
78.25.160.0/19 No ROA RIR databaseRIPE 672 100% 66
217.196.108.0/22 No ROA RIR databaseRIPE 672 100% 66
5.42.64.0/19 No ROA RIR databaseRIPE 671 100% 67

AS-SET

AS39493 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 152 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none2
  • Route object: not announced143
ChangePrefix or setDetailFull-table peers
ROA: origin5.42.96.0/19ROAs covering it name AS9123, not AS39493. If AS39493 should announce it, add a ROA for AS39493.63 of 673
Route object: none5.42.96.0/19No route object for it. Add a route object with origin AS39493 in the RIR database for the space.63 of 673
ROA: none217.196.106.0/24No ROA covers it. Add a ROA for AS39493, maxLength 24.671 of 673
Route object: none217.196.106.0/24No route object for it. Add a route object with origin AS39493 in the RIR database for the space.671 of 673
ROA: none5.42.0.0/18No ROA covers it. Add a ROA for AS39493, maxLength 18.673 of 673
ROA: none78.25.128.0/19No ROA covers it. Add a ROA for AS39493, maxLength 19.672 of 673
ROA: none78.25.160.0/19No ROA covers it. Add a ROA for AS39493, maxLength 19.672 of 673
ROA: none217.196.108.0/22No ROA covers it. Add a ROA for AS39493, maxLength 22.672 of 673
ROA: none5.42.64.0/19No ROA covers it. Add a ROA for AS39493, maxLength 19.671 of 673

Route objects not announced

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

5.42.0.0/21RIPENo ROA
5.42.0.0/24RIPENo ROA
5.42.1.0/24RIPENo ROA
5.42.2.0/24RIPENo ROA
5.42.3.0/24RIPENo ROA
5.42.4.0/24RIPENo ROA
5.42.5.0/24RIPENo ROA
5.42.6.0/24RIPENo ROA
5.42.7.0/24RIPENo ROA
5.42.8.0/21RIPENo ROA
5.42.8.0/24RIPENo ROA
5.42.9.0/24RIPENo ROA
5.42.10.0/24RIPENo ROA
5.42.11.0/24RIPENo ROA
5.42.12.0/24RIPENo ROA
5.42.13.0/24RIPENo ROA
5.42.14.0/24RIPENo ROA
5.42.15.0/24RIPENo ROA
5.42.16.0/21RIPENo ROA
5.42.16.0/24RIPENo ROA
5.42.17.0/24RIPENo ROA
5.42.18.0/24RIPENo ROA
5.42.19.0/24RIPENo ROA
5.42.20.0/24RIPENo ROA
5.42.21.0/24RIPENo ROA
5.42.22.0/24RIPENo ROA
5.42.23.0/24RIPENo ROA
5.42.24.0/21RIPENo ROA
5.42.24.0/24RIPENo ROA
5.42.25.0/24RIPENo ROA
5.42.26.0/24RIPENo ROA
5.42.27.0/24RIPENo ROA
5.42.28.0/24RIPENo ROA
5.42.29.0/24RIPENo ROA
5.42.30.0/24RIPENo ROA
5.42.31.0/24RIPENo ROA
5.42.32.0/21RIPENo ROA
5.42.32.0/24RIPENo ROA
5.42.33.0/24RIPENo ROA
5.42.34.0/24RIPENo ROA
5.42.35.0/24RIPENo ROA
5.42.36.0/24RIPENo ROA
5.42.37.0/24RIPENo ROA
5.42.38.0/24RIPENo ROA
5.42.39.0/24RIPENo ROA
5.42.40.0/21RIPENo ROA
5.42.40.0/24RIPENo ROA
5.42.41.0/24RIPENo ROA
5.42.42.0/24RIPENo ROA
5.42.43.0/24RIPENo ROA
5.42.44.0/24RIPENo ROA
5.42.45.0/24RIPENo ROA
5.42.46.0/24RIPENo ROA
5.42.47.0/24RIPENo ROA
5.42.48.0/21RIPENo ROA
5.42.48.0/24RIPENo ROA
5.42.49.0/24RIPENo ROA
5.42.50.0/24RIPENo ROA
5.42.51.0/24RIPENo ROA
5.42.52.0/24RIPENo ROA
5.42.53.0/24RIPENo ROA
5.42.54.0/24RIPENo ROA
5.42.55.0/24RIPENo ROA
5.42.56.0/24RIPENo ROA
5.42.57.0/24RIPENo ROA
5.42.58.0/24RIPENo ROA
5.42.59.0/24RIPENo ROA
5.42.60.0/24RIPENo ROA
5.42.61.0/24RIPENo ROA
5.42.62.0/24RIPENo ROA
5.42.63.0/24RIPENo ROA
5.42.64.0/20RIPEValid
5.42.65.0/24RIPEValid
5.42.66.0/24RIPEValid
5.42.80.0/21RIPENo ROA
5.42.89.0/24RIPENo ROA
5.42.90.0/23RIPENo ROA
5.42.92.0/22RIPENo ROA
78.25.128.0/20RIPENo ROA
78.25.128.0/24RIPENo ROA
78.25.129.0/24RIPENo ROA
78.25.130.0/24RIPENo ROA
78.25.131.0/24RIPENo ROA
78.25.132.0/24RIPENo ROA
78.25.133.0/24RIPENo ROA
78.25.134.0/24RIPENo ROA
78.25.135.0/24RIPENo ROA
78.25.136.0/24RIPENo ROA
78.25.137.0/24RIPENo ROA
78.25.138.0/24RIPENo ROA
78.25.139.0/24RIPENo ROA
78.25.140.0/24RIPENo ROA
78.25.141.0/24RIPENo ROA
78.25.142.0/24RIPENo ROA
78.25.143.0/24RIPENo ROA
78.25.144.0/24RIPENo ROA
78.25.145.0/24RIPENo ROA
78.25.146.0/24RIPENo ROA
78.25.147.0/24RIPENo ROA
78.25.148.0/24RIPENo ROA
78.25.149.0/24RIPENo ROA
78.25.150.0/24RIPENo ROA
78.25.151.0/24RIPENo ROA
78.25.152.0/24RIPENo ROA
78.25.153.0/24RIPENo ROA
78.25.154.0/24RIPENo ROA
78.25.155.0/24RIPENo ROA
78.25.156.0/24RIPENo ROA
78.25.157.0/24RIPENo ROA
78.25.158.0/24RIPENo ROA
78.25.159.0/24RIPENo ROA
78.25.160.0/24RIPENo ROA
78.25.161.0/24RIPENo ROA
78.25.162.0/24RIPENo ROA
78.25.163.0/24RIPENo ROA
78.25.164.0/24RIPENo ROA
78.25.165.0/24RIPENo ROA
78.25.166.0/24RIPENo ROA
78.25.167.0/24RIPENo ROA
78.25.168.0/24RIPENo ROA
78.25.169.0/24RIPENo ROA
78.25.170.0/24RIPENo ROA
78.25.171.0/24RIPENo ROA
78.25.172.0/24RIPENo ROA
78.25.173.0/24RIPENo ROA
78.25.174.0/24RIPENo ROA
78.25.175.0/24RIPENo ROA
78.25.176.0/24RIPENo ROA
78.25.177.0/24RIPENo ROA
78.25.178.0/24RIPENo ROA
78.25.179.0/24RIPENo ROA
78.25.180.0/24RIPENo ROA
78.25.181.0/24RIPENo ROA
78.25.182.0/24RIPENo ROA
78.25.183.0/24RIPENo ROA
78.25.184.0/24RIPENo ROA
78.25.185.0/24RIPENo ROA
78.25.186.0/24RIPENo ROA
78.25.187.0/24RIPENo ROA
78.25.188.0/24RIPENo ROA
78.25.189.0/24RIPENo ROA
78.25.190.0/24RIPENo ROA
78.25.191.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.