Skip to content

Autonomous System

AS31133 · PJSC MegaFon

Overview

AS31133 is announced on the Internet: RIPE RIS route collectors currently see 484 IPv4 prefixes and 66 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 825,088 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 119 upstream neighbours (transit providers or peers) and 911 downstream neighbours (customers or networks it carries). Its most visible upstreams are Hurricane Electric LLC (AS6939), Arelion Sweden AB (AS1299), and TELECOM ITALIA SPARKLE S.p.A. (AS6762). AS31133 was assigned by RIPE NCC, and its registration country is Russia.

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

Go further

Trace a route to this networkOpen in the BGP viewerWHOIS of 178.176.0.1

The trace goes to 178.176.0.1, the first address of 178.176.0.0/14. 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 (484 prefixes)

PrefixAddresses
31.173.0.0/1665,536
31.173.128.0/24256
31.173.129.0/24256
31.173.130.0/23512
31.173.136.0/24256
31.173.137.0/24256
31.173.138.0/24256
31.173.139.0/24256
31.173.140.0/24256
31.173.141.0/24256
31.173.142.0/24256
31.173.144.0/24256
31.173.147.0/24256
31.173.148.0/24256
31.173.149.0/24256
31.173.150.0/24256
31.173.151.0/24256
31.173.152.0/24256
31.173.153.0/24256
31.173.154.0/24256
31.173.155.0/24256
31.173.156.0/24256
31.173.157.0/24256
31.173.158.0/24256
31.173.159.0/24256
31.173.160.0/221,024
31.173.164.0/24256
31.173.165.0/24256
31.173.166.0/24256
31.173.167.0/24256
31.173.168.0/24256
31.173.169.0/24256
31.173.170.0/24256
31.173.171.0/24256
31.173.172.0/24256
31.173.173.0/24256
31.173.174.0/24256
31.173.175.0/24256
31.173.177.0/24256
31.173.178.0/24256
31.173.180.0/24256
31.173.181.0/24256
31.173.182.0/24256
31.173.183.0/24256
31.173.184.0/24256
31.173.185.0/24256
31.173.186.0/24256
31.173.187.0/24256
31.173.188.0/24256
31.173.189.0/24256
31.173.190.0/24256
31.173.191.0/24256
31.173.224.0/24256
31.173.234.0/24256
31.173.240.0/23512
37.28.160.0/198,192
37.28.185.0/24256
37.28.187.0/24256
37.28.188.0/23512
37.29.0.0/1732,768
37.29.0.0/24256
37.29.2.0/24256
37.29.3.0/24256
37.29.4.0/24256
37.29.5.0/24256
37.29.6.0/24256
37.29.7.0/24256
37.29.8.0/24256
37.29.9.0/24256
37.29.10.0/24256
37.29.11.0/24256
37.29.12.0/24256
37.29.14.0/24256
37.29.15.0/24256
37.29.16.0/24256
37.29.17.0/24256
37.29.19.0/24256
37.29.20.0/24256
37.29.21.0/24256
37.29.23.0/24256
37.29.24.0/24256
37.29.25.0/24256
37.29.26.0/24256
37.29.27.0/24256
37.29.40.0/24256
37.29.41.0/24256
37.29.42.0/24256
37.29.73.0/24256
37.29.78.0/24256
37.29.79.0/24256
37.29.88.0/24256
37.29.90.0/24256
37.29.92.0/23512
37.29.96.0/204,096
37.29.96.0/24256
37.29.97.0/24256
37.29.98.0/24256
37.29.99.0/24256
37.29.100.0/24256
37.29.101.0/24256

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

IPv6 prefixes (66 prefixes)

Prefix
2a03:d000:2000::/36
2a03:d000:2120::/48
2a03:d000:21e1::/48
2a03:d000:22c1::/48
2a03:d000:22e1::/48
2a03:d000:2341::/48
2a03:d000:2461::/48
2a03:d000:24a1::/48
2a03:d000:2661::/48
2a03:d000:26a1::/48
2a03:d000:2761::/48
2a03:d000:2781::/48
2a03:d000:27c3::/48
2a03:d000:2821::/48
2a03:d000:2921::/48
2a03:d000:2980::/43
2a03:d000:2981::/48
2a03:d000:29a1::/48
2a03:d000:2c02::/48
2a03:d000:2d00::/48
2a03:d000:3000::/40
2a03:d000:3200::/40
2a03:d000:3200::/41
2a03:d000:3280::/41
2a03:d000:3301::/48
2a03:d000:33c0::/48
2a03:d000:3800::/42
2a03:d000:3880::/42
2a03:d000:5200::/41
2a03:d000:5280::/41
2a03:d000:6400::/40
2a03:d000:6600::/42
2a03:d000:6640::/42
2a03:d000:67ff::/48
2a03:d000:6801::/48
2a03:d000:6c00::/48
2a03:d000:7000::/40
2a03:d000:7100::/40
2a03:d000:7100::/41
2a03:d000:7301::/48
2a03:d000:7302::/48
2a03:d000:7303::/48
2a03:d000:7380::/48
2a03:d000:8400::/41
2a03:d000:8480::/41
2a03:d000:8500::/41
2a03:d000:8580::/41
2a03:d000:8600::/41
2a03:d000:8701::/48
2a03:d000:8702::/48
2a03:d000:8780::/48
2a03:d002::/40
2a03:d007::/40
2a03:d007:100::/40
2a03:d007:200::/40
2a03:d007:300::/40
2a03:d007:400::/40
2a03:d007:500::/40
2a03:d007:600::/40
2a03:d007:700::/40
2a03:d007:800::/40
2a03:d007:900::/40
2a03:d007:a00::/40
2a03:d007:b00::/40
2a03:d007:c00::/40
2a03:d007:d00::/40

Neighbours

Upstreams (transit or peers) (119)

ASNetworkVisibility
AS6939Hurricane Electric LLC30,414
AS1299Arelion Sweden AB27,008
AS6762TELECOM ITALIA SPARKLE S.p.A.20,761
AS23764CTGNet13,797
AS9198JSC Kazakhtelecom7,179
AS13030Init7 (Switzerland) Ltd.4,906
AS9002RETN Limited4,390
AS6461Zayo Bandwidth4,037
AS24961WIIT AG2,647
AS34549meerfarbig GmbH & Co. KG2,178
AS31500Global Network Management Inc2,112
AS50304Blix Solutions AS2,085
AS4637Telstra Global2,032
AS33891Core-Backbone GmbH1,958
AS6696VERIXI SA1,917
AS8298IPng Networks GmbH1,774
AS21320-1,766
AS5405Inter.link GmbH1,697
AS35280F5 Networks SARL1,694
AS8455-1,686
AS25091IP-Max SA1,668
AS12779IT.Gate S.p.A.1,470
AS8218Zayo Infrastructure France SA1,452
AS14840BR.Digital Telecom1,444
AS20764CJSC RASCOM1,360
AS24482SG.GS1,342
AS34019Hivane Association1,318
AS42708Glesys AB1,236
AS12859BIT BV1,174
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH1,168

The 30 most visible of 119.

Downstreams (customers) (911)

ASNetworkVisibility
AS25159PJSC MegaFon8,595
AS20632PJSC MegaFon7,942
AS35598INETCOM CARRIER LLC6,326
AS50928PJSC MegaFon6,186
AS23764CTGNet5,771
AS28910"Uzbektelekom" Joint Stock Company5,613
AS9198JSC Kazakhtelecom4,992
AS31261PJSC MegaFon4,304
AS206810GUP DNR "UGLETELECOM"3,972
AS201706SERVICEPIPE LLC3,966
AS35104-3,561
AS29648-3,354
AS56534-2,716
AS12714PJSC MegaFon2,615
AS60280Republican Unitary Enterprise "National Traffic Exchange Center"2,459
AS8641-2,442
AS31163-2,283
AS48084-2,258
AS199599-2,164
AS31208-2,119
AS28761CrimeaCom South LLC1,981
AS31195-1,939
AS44267-1,552
AS34757-1,542
AS47165Omskie kabelnye seti Ltd.1,452
AS2854LLC Orange Business Services1,449
AS41039-1,446
AS197394-1,337
AS24955JSC "Ufanet"1,329
AS12418-1,305

The 30 most visible of 911.

630 more neighbours appear on both sides of this network depending on the path, so they are counted in neither list.

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.