Skip to content

Autonomous System

AS42291 · OOO Istranet

Overview

AS42291 is announced on the Internet: RIPE RIS route collectors currently see 8 IPv4 prefixes and 1 IPv6 prefix originated by this network. Together, its IPv4 prefixes cover 6,144 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 19 upstream neighbours (transit providers or peers) and 8 downstream neighbours (customers or networks it carries). Its most visible upstreams are Transroute Telecom LTD (AS50509), RETN Limited (AS9002), and PJSC Rostelecom (AS12389). AS42291 was assigned by RIPE NCC, and its registration country is Russia.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 17, 2026 at 1:08 AM UTC. This page is refreshed at most every 12 hours.

Go further

The trace goes to 176.62.176.1, the first address of 176.62.176.0/20. 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 (8 prefixes)

PrefixAddresses
91.192.20.0/221,024
91.192.20.0/24256
176.62.176.0/204,096
176.62.176.0/221,024
176.62.180.0/221,024
176.62.184.0/221,024
176.62.188.0/221,024
185.13.44.0/221,024

IPv6 prefixes (1 prefix)

Prefix
2a01:4080::/32

Neighbours

Upstreams (transit or peers) (19)

ASNetworkVisibility
AS50509Transroute Telecom LTD1,007
AS9002RETN Limited628
AS12389PJSC Rostelecom407
AS31500Global Network Management Inc314
AS62255BiMajLink d.o.o.308
AS35598INETCOM CARRIER LLC240
AS3216PJSC "Vimpelcom"188
AS57304JSC "RetnNet"179
AS8641LLC "Nauka-Svyaz"47
AS25091IP-Max SA17
AS47692Nessus GmbH12
AS9198JSC Kazakhtelecom7
AS15958CETIN Ltd. Belgrade7
AS6204INTERKVM HOST SRL6
AS42295TBISS Ltd6
AS60171AFR-IX TELECOM S.A.6
AS62000SERVERD SAS4
AS137409GSL Networks Pty LTD4
AS50673Serverius Holding B.V.3

Downstreams (customers) (8)

ASNetworkVisibility
AS216363OOO Istra.net793
AS205439IP PARK LLC791
AS216247OOO SITI LAJT575
AS62426JSC ESTEIT INVEST212
AS49825Lantek LLC189
AS44093JSC ESTEIT INVEST178
AS47860OOO "OTC"133
AS47213"IKA Telecom" LTD121

18 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.