bgpreport

Network · data from 2026-11-12

AS43148 MTS-KURGAN-AS MTS PJSC

Registry name: MTS-KURGAN-AS MTS PJSC, RU · not in PeeringDB

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

Announced routes

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

89.31.37.0/24 No ROA Nonecovered by 89.31.32.0/21 671 100% 67
89.31.38.0/24 No ROA Nonecovered by 89.31.32.0/21 671 100% 67
89.31.39.0/24 No ROA Nonecovered by 89.31.32.0/21 671 100% 67
95.139.70.0/24 No ROA None 671 100% 67
185.25.16.0/24 No ROA Nonecovered by 185.25.16.0/22 671 100% 67
185.25.17.0/24 No ROA Nonecovered by 185.25.16.0/22 671 100% 67
185.25.18.0/24 No ROA Nonecovered by 185.25.16.0/22 671 100% 67
185.25.19.0/24 No ROA Nonecovered by 185.25.16.0/22 671 100% 67
78.108.64.0/20 No ROA RIR databaseRIPE 673 100% 67
89.31.32.0/21 No ROA RIR databaseRIPE 673 100% 67
95.129.160.0/21 No ROA RIR databaseRIPE 673 100% 67
31.29.184.0/22 No ROA RIR databaseRIPE 671 100% 67
95.129.166.0/24 No ROA RIR databaseRIPE 671 100% 67

AS-SET

AS43148 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 40 are in fix.csv.

  • ROA: none13
  • Route object: none8
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none89.31.37.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none89.31.37.0/24No route object for it. A route object for 89.31.32.0/21 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none89.31.38.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none89.31.38.0/24No route object for it. A route object for 89.31.32.0/21 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none89.31.39.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none89.31.39.0/24No route object for it. A route object for 89.31.32.0/21 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none95.139.70.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none95.139.70.0/24No route object for it. Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none185.25.16.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none185.25.16.0/24No route object for it. A route object for 185.25.16.0/22 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none185.25.17.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none185.25.17.0/24No route object for it. A route object for 185.25.16.0/22 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none185.25.18.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none185.25.18.0/24No route object for it. A route object for 185.25.16.0/22 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none185.25.19.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673
Route object: none185.25.19.0/24No route object for it. A route object for 185.25.16.0/22 with origin AS43148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43148 in the RIR database for the space.671 of 673
ROA: none78.108.64.0/20No ROA covers it. Add a ROA for AS43148, maxLength 20.673 of 673
ROA: none89.31.32.0/21No ROA covers it. Add a ROA for AS43148, maxLength 21.673 of 673
ROA: none95.129.160.0/21No ROA covers it. Add a ROA for AS43148, maxLength 21.673 of 673
ROA: none31.29.184.0/22No ROA covers it. Add a ROA for AS43148, maxLength 22.671 of 673
ROA: none95.129.166.0/24No ROA covers it. Add a ROA for AS43148, maxLength 24.671 of 673

Route objects not announced

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

78.108.64.0/21RIPENo ROA
78.108.64.0/23RIPENo ROA
78.108.66.0/24RIPENo ROA
78.108.67.0/24RIPENo ROA
78.108.68.0/24RIPENo ROA
78.108.69.0/24RIPENo ROA
78.108.70.0/24RIPENo ROA
78.108.71.0/24RIPENo ROA
78.108.72.0/21RIPENo ROA
78.108.73.0/24RIPENo ROA
78.108.74.0/24RIPENo ROA
78.108.75.0/24RIPENo ROA
78.108.76.0/24RIPENo ROA
78.108.77.0/24RIPENo ROA
78.108.78.0/24RIPENo ROA
78.108.79.0/24RIPENo ROA
95.129.160.0/22RIPENo ROA
95.129.164.0/22RIPENo ROA
185.25.16.0/22RIPENo 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.