Skip to content

Autonomous System

AS7065 · Sonic.net, LLC

Overview

AS7065 is announced on the Internet: RIPE RIS route collectors currently see 38 IPv4 prefixes and 2 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 182,016 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 5 upstream neighbours (transit providers or peers) and no downstream neighbour (customers or networks it carries). Its most visible upstreams are Sonic Telecom LLC (AS46375), Arelion Sweden AB (AS1299), and Cogent Communications, LLC (AS174). AS7065 was assigned by ARIN, and its registration country is United States.

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

Go further

The trace goes to 50.1.128.1, the first address of 50.1.128.0/17. 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 (38 prefixes)

PrefixAddresses
50.0.2.0/23512
50.0.8.0/23512
50.0.10.0/23512
50.0.208.0/204,096
50.1.0.0/204,096
50.1.16.0/204,096
50.1.32.0/204,096
50.1.64.0/221,024
50.1.68.0/24256
50.1.128.0/1732,768
64.142.0.0/198,192
64.142.48.0/204,096
64.142.96.0/198,192
65.214.144.0/221,024
69.12.128.0/198,192
69.12.160.0/198,192
69.12.176.0/204,096
69.12.208.0/204,096
70.36.160.0/221,024
70.36.164.0/221,024
70.36.168.0/212,048
70.36.208.0/204,096
75.101.112.0/212,048
76.191.224.0/212,048
76.191.248.0/212,048
108.169.64.0/1816,384
157.131.0.0/204,096
184.23.64.0/1816,384
184.23.148.0/221,024
184.23.168.0/221,024
184.23.176.0/204,096
208.106.56.0/221,024
208.106.80.0/212,048
208.106.112.0/212,048
208.106.120.0/221,024
208.201.224.0/198,192
209.204.128.0/198,192
209.204.160.0/198,192

IPv6 prefixes (2 prefixes)

Prefix
2001:5a8:200::/40
2607:43c0::/33

Neighbours

Upstreams (transit or peers) (5)

ASNetworkVisibility
AS46375Sonic Telecom LLC702
AS1299Arelion Sweden AB390
AS174Cogent Communications, LLC340
AS6453TATA COMMUNICATIONS (AMERICA) INC331
AS1239Cogent Communications, LLC1

Downstreams (customers) (0)

None seen.

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.