subnet.im

AS43038MTS PJSC

RussiaRegistryRIPE NCCTypeEyeball

As of 11th November 2026, AS43038 (MTS PJSC), an access network registered in Russia with RIPE NCC, originates 15 IPv4 prefixes covering 7.2k addresses. By IPv4 address space that makes it the 13,291st-largest of the 80,763 networks we see originating IPv4, and the 781st-largest of 4,985 in Russia. It is seen behind 1 upstream network, most often AS8359 (MTS PJSC). 7% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 100% of its routes reach at least 90% of full-feed peers.

At a glance

IPv4 prefixes

15

IPv6 prefixes

0

IPv4 addresses

7.2k

IPv6 /64s

0

Upstream graph

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

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

Networks observed one and two hops upstream of AS43038 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 AS43038
NetworkCountryRelationshipPathsVantage pts
AS8359MTS PJSCRUPeer1,15577

Prefixes

The largest blocks AS43038 originates, widest first.

Largest prefixes originated by AS43038
PrefixAddressesVisibility
178.17.184.0/221k77/77
178.17.188.0/221k77/77
178.17.176.0/2351277/77
178.17.178.0/2351277/77
178.17.180.0/2351277/77
178.17.182.0/2351277/77
193.33.230.0/2351277/77
213.176.232.0/2351277/77
213.176.234.0/2351277/77
79.143.229.0/2425677/77

Routing health

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

  • Valid6.7%1
  • Invalid0.0%0
  • No ROA93.3%14

Propagation

  • Globally propagated90% of full-feed peers or more100.0%15
  • 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 AS43038 started or stopped in this period.

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