Skip to content

Autonomous System

AS25106 · Mobile TeleSystems JLLC

Overview

AS25106 is announced on the Internet: RIPE RIS route collectors currently see 195 IPv4 prefixes and 34 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 250,112 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 3 upstream neighbours (transit providers or peers) and 9 downstream neighbours (customers or networks it carries). Its most visible upstreams are Republican Unitary Telecommunication Enterprise Beltelecom (AS6697), Belarusian Cloud Technologies LLC (AS60330), and Republican Unitary Enterprise "National Traffic Exchange Center" (AS60280). AS25106 was assigned by RIPE NCC, and its registration country is Belarus.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 16, 2026 at 11:01 PM UTC. This page is refreshed at most every 12 hours.

Go further

The trace goes to 46.216.0.1, the first address of 46.216.0.0/17. An address picked inside a prefix may not answer (nothing listens there, or the network filters probes): the trace then shows the path up to the last network that replies.

Announced prefixes

IPv4 prefixes (195 prefixes)

PrefixAddresses
46.56.40.0/212,048
46.56.41.0/24256
46.56.48.0/23512
46.56.50.0/23512
46.56.52.0/23512
46.56.54.0/23512
46.56.56.0/221,024
46.56.58.0/24256
46.56.59.0/24256
46.56.60.0/24256
46.56.61.0/24256
46.56.62.0/23512
46.56.64.0/198,192
46.56.84.0/24256
46.56.85.0/24256
46.56.86.0/24256
46.56.88.0/24256
46.56.89.0/24256
46.56.96.0/198,192
46.56.118.0/24256
46.56.119.0/24256
46.56.126.0/24256
46.56.127.0/24256
46.216.0.0/1732,768
46.216.64.0/204,096
46.216.88.0/23512
46.216.96.0/24256
46.216.97.0/24256
46.216.98.0/23512
46.216.100.0/23512
46.216.103.0/24256
46.216.128.0/1816,384
46.216.143.0/24256
46.216.168.0/221,024
46.216.184.0/212,048
46.216.192.0/1816,384
46.216.192.0/24256
46.216.194.0/24256
46.216.195.0/24256
46.216.200.0/24256
46.216.208.0/24256
46.216.216.0/24256
46.216.218.0/24256
46.216.219.0/24256
46.216.220.0/24256
46.216.221.0/24256
46.216.223.0/24256
46.216.246.0/24256
46.216.249.0/24256
46.216.251.0/24256
46.216.252.0/24256
46.216.253.0/24256
46.216.254.0/24256
87.252.242.0/24256
87.252.243.0/24256
93.125.123.0/24256
95.130.84.0/24256
134.17.0.0/204,096
134.17.4.0/221,024
134.17.14.0/24256
134.17.15.0/24256
134.17.16.0/212,048
134.17.16.0/24256
134.17.17.0/24256
134.17.24.0/212,048
134.17.24.0/221,024
134.17.28.0/24256
134.17.32.0/198,192
134.17.32.0/221,024
134.17.64.0/204,096
134.17.79.0/24256
134.17.80.0/212,048
134.17.80.0/221,024
134.17.88.0/212,048
134.17.88.0/24256
134.17.89.0/24256
134.17.92.0/24256
134.17.94.0/24256
134.17.95.0/24256
134.17.96.0/198,192
134.17.124.0/24256
134.17.128.0/198,192
134.17.128.0/212,048
134.17.136.0/212,048
134.17.144.0/204,096
134.17.160.0/198,192
134.17.192.0/198,192
134.17.208.0/204,096
134.17.208.0/221,024
134.17.209.0/24256
134.17.210.0/23512
134.17.212.0/23512
134.17.215.0/24256
134.17.223.0/24256
134.17.224.0/204,096
134.17.224.0/24256
134.17.225.0/24256
134.17.226.0/23512
134.17.229.0/24256
176.60.0.0/1816,384

Showing the first 100 of 195, in address order. Complete list on RIPEstat

IPv6 prefixes (34 prefixes)

Prefix
2a02:bf0::/32
2a02:bf0::/48
2a02:bf0:1::/48
2a02:bf0:2::/48
2a02:bf0:6::/48
2a02:bf0:25::/48
2a02:bf0:26::/48
2a02:bf0:27::/48
2a02:bf0:28::/48
2a02:bf0:29::/48
2a02:bf0:100::/44
2a02:bf0:110::/44
2a02:bf0:1000::/36
2a02:bf0:1002::/48
2a02:bf0:1003::/48
2a02:bf0:1100::/40
2a02:bf0:1c00::/44
2a02:bf0:1c10::/44
2a02:bf0:3000::/36
2a02:bf0:3200::/44
2a02:bf0:3220::/44
2a02:bf0:3230::/44
2a02:bf0:4000::/36
2a02:bf0:4a00::/44
2a02:bf0:4a10::/44
2a02:bf0:5000::/36
2a02:bf0:5a00::/44
2a02:bf0:5a10::/44
2a02:bf0:6000::/36
2a02:bf0:6810::/44
2a02:bf0:6820::/44
2a02:bf0:7000::/36
2a02:bf0:7810::/44
2a02:bf0:7820::/44

Neighbours

Upstreams (transit or peers) (3)

ASNetworkVisibility
AS6697Republican Unitary Telecommunication Enterprise Beltelecom2,070
AS60330Belarusian Cloud Technologies LLC1,724
AS60280Republican Unitary Enterprise "National Traffic Exchange Center"1

Downstreams (customers) (9)

ASNetworkVisibility
AS13171Belarusian State University294
AS57135Open joint-stock company "Naftan"291
AS48340Axioma-Service Limited284
AS50205Banking and Financial Network JSC284
AS206428MEGADATA LLC284
AS213664Idea Host Ltd284
AS62170JSC Sberbank78
AS211487LLC "BROKERAGE HOUSE "ATLANT-M"10
AS49526JSC MTBank2

Visibility is RIPEstat's count of how often the route collectors observed the link. It compares neighbours with each other; it is not a traffic volume.

How to read this page

An Autonomous System (AS) is a network run under one routing policy: an internet provider, a cloud, a content network, a university. Each one has a number, its ASN, assigned by a regional registry (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC), and uses BGP, the protocol networks use to tell each other where addresses are, to announce the blocks of addresses it delivers to.

A prefix such as 203.0.113.0/24 is a block of addresses: the number after the slash says how many bits are fixed, so a /24 holds 256 IPv4 addresses and a /16 holds 65,536. Networks often announce a large block and smaller pieces of it at the same time, which is why the address total counts each address once.

Neighbours come from the paths themselves. A network that appears just before this one in a path, on the collector's side, is an upstream: a transit provider or a peer. One that appears just after it is a downstream, usually a customer. Peering at an internet exchange also shows up as an upstream, so the upstream list is not a list of paid transit.

The data comes from RIPEstat, run by the RIPE NCC, which gathers the routing tables of hundreds of networks through its RIS route collectors. This page reads it when it is visited and keeps it for 12 hours at most; the BGP viewer reads it live.

Frequently asked questions

How do I find the ASN of an IP address?
Type the address in the BGP viewer: it shows the prefix that covers it, the AS that originates that prefix and the paths seen towards it. A traceroute also names the network of each hop, so you can see every AS a connection crosses.
Why does one company have several ASNs?
Large operators split their network by region, by activity or by history: a cloud may use one number for its backbone and another for a region, and every acquisition brings its own numbers. Each number has its own page, with its own prefixes and neighbours.
Why do prefix counts differ from one site to another?
Each source sees the routing table from different collectors, at a different time, and counts differently: some include prefixes withdrawn in recent weeks, some merge a block and its pieces. This page counts the prefixes RIPE RIS collectors see originated by the network at the end of the latest two-week window, and counts each IPv4 address once.
Is this the list of IP ranges of a cloud provider?
It is what its networks announce, which is what the Internet routes to them. Many providers also publish an official list of ranges per service and region; that list is the reference for firewall rules, because a range can be announced before it is used, or announced by another of their AS numbers.