Skip to content

Autonomous System

AS16117 · Gavle Energi AB

Overview

AS16117 is announced on the Internet: RIPE RIS route collectors currently see 5 IPv4 prefixes and 1 IPv6 prefix originated by this network. Together, its IPv4 prefixes cover 29,696 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 15 upstream neighbours (transit providers or peers) and 11 downstream neighbours (customers or networks it carries). Its most visible upstreams are GlobalConnect AB (AS12552), Hurricane Electric LLC (AS6939), and Inter.link GmbH (AS5405). AS16117 was assigned by RIPE NCC, and its registration country is Sweden.

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

Go further

The trace goes to 62.116.224.1, the first address of 62.116.224.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 (5 prefixes)

PrefixAddresses
62.116.224.0/198,192
79.142.208.0/204,096
84.23.128.0/198,192
185.98.244.0/221,024
213.141.64.0/198,192

IPv6 prefixes (1 prefix)

Prefix
2001:b48::/29

Neighbours

Upstreams (transit or peers) (15)

ASNetworkVisibility
AS12552GlobalConnect AB3,437
AS6939Hurricane Electric LLC884
AS5405Inter.link GmbH68
AS35280F5 Networks SARL64
AS20764CJSC RASCOM53
AS4455IX Reach Ltd26
AS50304Blix Solutions AS25
AS1257Tele2 Sverige AB23
AS14840BR.Digital Telecom22
AS20473The Constant Company, LLC11
AS22356Durand do Brasil Ltda11
AS25091IP-Max SA9
AS33891Core-Backbone GmbH8
AS13194UAB "Bite Lietuva"1
AS52005-1

Downstreams (customers) (11)

ASNetworkVisibility
AS31507Servanet AB701
AS20626Sandviken Energi AB519
AS25417Ljusnet AB392
AS20625Bollnas energi AB389
AS28847Soderhamn NARA AB387
AS60213Helsinge Net Ovanaker AB387
AS41848Gavle kommun386
AS28954Fiberstaden AB385
AS206114Gavle Energi AB385
AS212725Ovanakers kommun269
AS202111-181

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