Skip to content

Autonomous System

AS265680 ยท HNTELCO S.A

Overview

AS265680 is announced on the Internet: RIPE RIS route collectors currently see 4 IPv4 prefixes and 1 IPv6 prefix originated by this network. Together, its IPv4 prefixes cover 1,024 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 16 upstream neighbours (transit providers or peers) and 14 downstream neighbours (customers or networks it carries). Its most visible upstreams are Zayo Bandwidth (AS6461), Hurricane Electric LLC (AS6939), and Cogent Communications, LLC (AS174). AS265680 was assigned by LACNIC, and its registration country is Honduras.

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

Go further

The trace goes to 45.5.76.1, the first address of 45.5.76.0/24. 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 (4 prefixes)

PrefixAddresses
45.5.76.0/24256
45.5.77.0/24256
45.5.78.0/24256
45.5.79.0/24256

IPv6 prefixes (1 prefix)

Prefix
2803:21c0::/32

Neighbours

Upstreams (transit or peers) (16)

ASNetworkVisibility
AS6461Zayo Bandwidth1,613
AS6939Hurricane Electric LLC1,149
AS174Cogent Communications, LLC1,120
AS1299Arelion Sweden AB814
AS3257GTT Communications Inc.718
AS23520Columbus Networks USA, Inc.245
AS25091IP-Max SA83
AS14840BR.Digital Telecom24
AS37468Angola Cables24
AS8359MTS PJSC23
AS4230CLARO S.A.22
AS286GTT Communications Inc.15
AS27923-13
AS137409GSL Networks Pty LTD12
AS22356Durand do Brasil Ltda10
AS394625-6

Downstreams (customers) (14)

ASNetworkVisibility
AS269800NTERCONEXION HN S.A478
AS265849HONDURAS ADELANTE SA472
AS265827CAPITALFUTURO SA471
AS266827BOHO BEACH CLUB S.A.447
AS266842HNHOSTING.NET S.A.447
AS265671PODOJIL CONTRACTING, S.A.444
AS265770GRUPO LANA, S.A.419
AS272825ELRIC DISENOS DE HONDURAS, S.A.394
AS266820HAMMERHEAD DIVE S.A.383
AS265753CW HOLDINGS, S.A.315
AS264658-308
AS265850-253
AS266865-253
AS269866-253

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