Skip to content

Autonomous System

AS34056 · Kyiv Optic Networks ltd

Overview

AS34056 is announced on the Internet: RIPE RIS route collectors currently see 3 IPv4 prefixes and 1 IPv6 prefix originated by this network. Together, its IPv4 prefixes cover 17,408 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 15 upstream neighbours (transit providers or peers) and 15 downstream neighbours (customers or networks it carries). Its most visible upstreams are Filanco Ukraine Ltd. (AS57455), Fiord Networks, UAB (AS28917), and Hurricane Electric LLC (AS6939). AS34056 was assigned by RIPE NCC, and its registration country is Ukraine.

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

Go further

The trace goes to 92.244.96.1, the first address of 92.244.96.0/19. 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 (3 prefixes)

PrefixAddresses
46.229.48.0/221,024
92.244.96.0/198,192
109.108.64.0/198,192

IPv6 prefixes (1 prefix)

Prefix
2a00:1688::/48

Neighbours

Upstreams (transit or peers) (15)

ASNetworkVisibility
AS57455Filanco Ukraine Ltd.1,244
AS28917Fiord Networks, UAB900
AS6939Hurricane Electric LLC767
AS9002RETN Limited732
AS174Cogent Communications, LLC456
AS35297Dataline LLC374
AS50263A-Systems Sp. z o.o.90
AS3303Swisscom (Schweiz) AG42
AS49434FBW NETWORKS SAS21
AS29632Netassist International EOOD9
AS30886PP KOM i TEX2
AS48648K-Link LLC2
AS60812-2
AS6204INTERKVM HOST SRL1
AS42295TBISS Ltd1

Downstreams (customers) (15)

ASNetworkVisibility
AS44668Zubko Volodymyr Viktorovych767
AS206791Slobozhenyuk B.Y. PE591
AS41917Happylink LLC584
AS201948ITKOM PE502
AS207858Dmytro Moiseiev324
AS207560Zubritska Valeriia Nikolaevna296
AS213159FOP Klimanov Eugene Alexandrovich296
AS198593RENDEZ VOUS LLC294
AS49139PE Prujmak Olexandr Olegovich288
AS209825Katanytsia Lyubov Viktorivna117
AS198227-35
AS48438-16
AS44526-12
AS43409-11
AS210050-11

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