bgpreport

Network · data from 2026-11-12

AS13174 MTSNet MTS PJSC

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

12IPv4 routes 75.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS13174, seen from no peer

Announced routes

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

91.207.84.0/24 No ROA RIR databaseRIPE 671 100% 67
91.216.167.0/24 No ROA RIR databaseRIPE 671 100% 67
194.54.148.0/22 No ROA RIR databaseRIPE 671 100% 67
213.87.0.0/21 Valid RIR databaseRIPE 673 100% 67
213.87.16.0/21 Valid RIR databaseRIPE 673 100% 67
213.87.24.0/21 Valid RIR databaseRIPE 673 100% 67
213.87.32.0/23 Valid RIR databaseRIPE 671 100% 67
213.87.36.0/22 Valid RIR databaseRIPE 671 100% 67
213.87.44.0/22 Valid RIR databaseRIPE 671 100% 67
213.87.48.0/22 Valid RIR databaseRIPE 671 100% 67
213.87.50.0/23 Valid RIR databaseRIPE 671 100% 67
213.87.52.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS13174 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 12 are in fix.csv.

  • ROA: none3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none91.207.84.0/24No ROA covers it. Add a ROA for AS13174, maxLength 24.671 of 673
ROA: none91.216.167.0/24No ROA covers it. Add a ROA for AS13174, maxLength 24.671 of 673
ROA: none194.54.148.0/22No ROA covers it. Add a ROA for AS13174, maxLength 22.671 of 673

Route objects not announced

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

46.23.176.0/20RIPENo ROA
62.105.48.0/22RIPENo ROA
62.105.52.0/22RIPENo ROA
213.87.0.0/19RIPEValid
213.87.32.0/21RIPEValid
213.87.48.0/21RIPEValid
213.87.64.0/22RIPEInvalid: origin
213.87.70.0/23RIPEInvalid: origin
213.87.80.0/20RIPEInvalid: origin

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.