subnet.im

AS42322MTS PJSC

RussiaRegistryRIPE NCCTypeEyeball

As of 27th September 2026, AS42322 (MTS PJSC), an access network registered in Russia with RIPE NCC, originates 13 IPv4 prefixes covering 4.1k addresses and 1 IPv6 prefix. By IPv4 address space that makes it the 17,073rd-largest of the 79,523 networks we see originating IPv4, and the 1,004th-largest of 4,942 in Russia. It is seen behind 1 upstream network, most often AS8359 (MTS PJSC). 29% of its announcements have a valid RPKI ROA; 7 are RPKI-invalid. 50% of its routes reach at least 90% of full-feed peers.

At a glance

IPv4 prefixes

13

IPv6 prefixes

1

IPv4 addresses

4.1k

IPv6 /64s

4.3B

Upstream graph

The networks AS42322 is seen behind, one and two hops out, drawn from real AS paths.

AS42322Toward the internet core
Upstream graph for AS42322: 3 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS42322MTS PJSCThis networkAS8359MTS PJSCAS1299Arelion (fka. Tel…AS18106Viewqwest Pte Ltd

Networks observed one and two hops upstream of AS42322 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

2

adjacent networks

Upstreams
150%
Peers
150%
Downstreams
00%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS42322
NetworkCountryRelationshipPathsVantage pts
AS8359MTS PJSCRUPeer718145

Prefixes

The largest blocks AS42322 originates, widest first.

Largest prefixes originated by AS42322
PrefixAddressesVisibility
37.19.72.0/2351281/81
37.19.76.0/2351281/81
109.201.66.0/2351224/81
46.20.176.0/2425681/81
46.20.177.0/2425681/81
46.20.178.0/2425681/81
46.20.179.0/2425681/81
46.20.189.0/2425624/81
46.20.191.0/2425624/81
109.201.64.0/2425624/81

Routing health

How AS42322's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid28.6%4
  • Invalid50.0%7
  • No ROA21.4%3

Propagation

  • Globally propagated90% of full-feed peers or more50.0%7
  • Partially propagated40% to 90%0.0%0
  • Seen by few peersUnder 40%50.0%7

Prefix sizes

IPv4 — 13 prefixes

IPv6 — 1 prefixes

  • /324.3B × /64100.0%1

Recent changes

Announcements that started or stopped since 28th Aug 2026.

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.