subnet.im

AS41822MTS PJSC

RussiaRegistryRIPE NCCTypeEyeball

As of 11th November 2026, AS41822 (MTS PJSC), an access network registered in Russia with RIPE NCC, originates 34 IPv4 prefixes covering 26.1k addresses. By IPv4 address space that makes it the 6,176th-largest of the 80,763 networks we see originating IPv4, and the 282nd-largest of 4,985 in Russia. It is seen behind 1 upstream network, most often AS8359 (MTS PJSC), and in front of 2 downstream networks. None of its announcements have a valid RPKI ROA. 100% of its routes reach at least 90% of full-feed peers.

At a glance

IPv4 prefixes

34

IPv6 prefixes

0

IPv4 addresses

26.1k

IPv6 /64s

0

Upstream graph

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

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

Networks observed one and two hops upstream of AS41822 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

6

adjacent networks

Upstreams
117%
Peers
350%
Downstreams
233%

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

Upstreams of AS41822
NetworkCountryRelationshipPathsVantage pts
AS8359MTS PJSCRUPeer3,05477

Prefixes

All 34

The largest blocks AS41822 originates, widest first.

Largest prefixes originated by AS41822
PrefixAddressesVisibility
46.250.64.0/212k77/77
92.246.192.0/212k77/77
109.198.64.0/212k77/77
46.250.72.0/221k77/77
46.250.84.0/221k77/77
46.250.88.0/221k77/77
46.250.92.0/221k77/77
91.143.48.0/221k77/77
91.143.52.0/221k77/77
91.143.56.0/221k77/77

Routing health

How AS41822'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

  • Valid0.0%0
  • Invalid0.0%0
  • No ROA100.0%34

Propagation

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

Prefix sizes

Recent changes

Announcements that started or stopped since 12th Oct 2026.

No announcement by AS41822 started or stopped in this period.

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