bgpreport

Network · data from 2026-11-12

AS197023 ASCOMTELTV MTS PJSC

Registry name: ASCOMTELTV MTS PJSC, RU · not in PeeringDB

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

Announced routes

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

46.172.0.0/19 No ROA Nonecovered by 46.172.0.0/18 673 100% 67
46.172.12.0/22 No ROA Nonecovered by 46.172.0.0/18 671 100% 67
46.172.28.0/22 No ROA Nonecovered by 46.172.0.0/18 671 100% 67
46.172.32.0/19 No ROA Nonecovered by 46.172.0.0/18 2 0%low visibility 2
178.216.72.0/22 No ROA Nonecovered by 178.216.72.0/21 2 0%low visibility 2
178.216.76.0/22 No ROA Nonecovered by 178.216.72.0/21 2 0%low visibility 2
46.172.0.0/18 No ROA RIR databaseRIPE 673 100% 67
178.216.72.0/21 No ROA RIR databaseRIPE 673 100% 67
84.17.236.0/24 No ROA RIR databaseRIPE 671 100% 67
84.17.246.0/24 No ROA RIR databaseRIPE 671 100% 67
81.195.131.0/24 Valid Other origin only 670 100% 67

AS-SET

AS197023 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 19 are in fix.csv.

  • ROA: none10
  • Route object: none7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none46.172.0.0/19No ROA covers it. Add a ROA for AS197023, maxLength 19.673 of 673
Route object: none46.172.0.0/19No route object for it. A route object for 46.172.0.0/18 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.673 of 673
ROA: none46.172.12.0/22No ROA covers it. Add a ROA for AS197023, maxLength 22.671 of 673
Route object: none46.172.12.0/22No route object for it. A route object for 46.172.0.0/18 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.671 of 673
ROA: none46.172.28.0/22No ROA covers it. Add a ROA for AS197023, maxLength 22.671 of 673
Route object: none46.172.28.0/22No route object for it. A route object for 46.172.0.0/18 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.671 of 673
ROA: none46.172.32.0/19No ROA covers it. Add a ROA for AS197023, maxLength 19.2 of 673
Route object: none46.172.32.0/19No route object for it. A route object for 46.172.0.0/18 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.2 of 673
ROA: none178.216.72.0/22No ROA covers it. Add a ROA for AS197023, maxLength 22.2 of 673
Route object: none178.216.72.0/22No route object for it. A route object for 178.216.72.0/21 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.2 of 673
ROA: none178.216.76.0/22No ROA covers it. Add a ROA for AS197023, maxLength 22.2 of 673
Route object: none178.216.76.0/22No route object for it. A route object for 178.216.72.0/21 with origin AS197023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197023 in the RIR database for the space.2 of 673
ROA: none46.172.0.0/18No ROA covers it. Add a ROA for AS197023, maxLength 18.673 of 673
ROA: none178.216.72.0/21No ROA covers it. Add a ROA for AS197023, maxLength 21.673 of 673
ROA: none84.17.236.0/24No ROA covers it. Add a ROA for AS197023, maxLength 24.671 of 673
ROA: none84.17.246.0/24No ROA covers it. Add a ROA for AS197023, maxLength 24.671 of 673
Route object: none81.195.131.0/24Route objects for it name AS8359. Add a route object with origin AS197023 in the RIR database for the space.670 of 673

Route objects not announced

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

84.17.226.0/24RIPENo ROA
2a03:7204::/32RIPENo 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.