Skip to content

Autonomous System

AS46887 · Crown Castle Fiber LLC

Overview

AS46887 is announced on the Internet: RIPE RIS route collectors currently see 800 IPv4 prefixes and 255 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 863,232 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 4 upstream neighbours (transit providers or peers) and 968 downstream neighbours (customers or networks it carries). Its most visible upstreams are Zayo Bandwidth (AS6461), USC / UFMG PEERING Research Testbed (AS47065), and GiGstreem (AS31769). AS46887 was assigned by ARIN, and its registration country is United States.

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

Go further

The trace goes to 9.179.0.1, the first address of 9.179.0.0/16. 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 (800 prefixes)

PrefixAddresses
8.11.166.0/24256
8.28.48.0/212,048
8.28.48.0/24256
8.28.53.0/24256
8.28.54.0/23512
8.28.54.0/24256
8.29.208.0/212,048
8.29.210.0/23512
8.29.210.0/24256
8.29.211.0/24256
8.29.212.0/221,024
8.41.200.0/24256
8.225.193.0/24256
9.179.0.0/1665,536
9.179.0.0/221,024
9.179.4.0/221,024
9.179.8.0/221,024
9.179.12.0/221,024
9.179.16.0/221,024
9.179.20.0/221,024
9.179.24.0/221,024
9.179.28.0/221,024
9.179.32.0/221,024
9.179.36.0/221,024
9.179.40.0/221,024
9.179.44.0/221,024
9.179.48.0/221,024
9.179.52.0/221,024
9.179.56.0/221,024
9.179.60.0/221,024
9.179.64.0/221,024
9.179.68.0/221,024
9.179.72.0/221,024
9.179.76.0/221,024
9.179.80.0/221,024
9.179.84.0/221,024
9.179.88.0/221,024
9.179.92.0/221,024
9.179.100.0/221,024
9.179.224.0/24256
9.179.228.0/24256
9.179.231.0/24256
9.179.233.0/24256
9.191.0.0/1665,536
23.161.184.0/24256
38.134.184.0/24256
38.147.220.0/24256
38.147.221.0/24256
64.20.160.0/212,048
64.20.162.0/24256
64.20.168.0/23512
64.20.170.0/23512
64.20.172.0/221,024
64.20.188.0/221,024
64.72.64.0/198,192
64.72.64.0/221,024
64.72.68.0/23512
64.72.72.0/24256
64.72.74.0/23512
64.72.76.0/24256
64.72.77.0/24256
64.72.78.0/24256
64.72.81.0/24256
64.72.84.0/221,024
64.72.88.0/23512
64.72.93.0/24256
64.72.95.0/24256
64.112.182.0/23512
64.189.34.0/24256
64.195.215.0/24256
64.238.128.0/212,048
64.238.128.0/24256
64.238.130.0/24256
64.238.132.0/221,024
64.238.136.0/23512
64.238.138.0/23512
64.238.140.0/23512
64.238.142.0/23512
65.254.0.0/204,096
65.254.4.0/24256
65.254.12.0/221,024
65.254.16.0/212,048
65.254.16.0/221,024
65.254.24.0/23512
65.254.28.0/23512
65.254.30.0/23512
66.37.32.0/204,096
66.37.32.0/23512
66.37.34.0/23512
66.37.36.0/24256
66.37.38.0/24256
66.37.40.0/23512
66.37.42.0/24256
66.37.43.0/24256
66.206.112.0/204,096
66.206.112.0/24256
66.206.114.0/24256
66.206.116.0/221,024
66.206.117.0/24256
66.206.120.0/24256

Showing the first 100 of 800, in address order. Complete list on RIPEstat

IPv6 prefixes (255 prefixes)

Prefix
2602:810:20c6::/48
2602:810:20c7::/48
2604:200:1f::/48
2604:200:1500::/48
2604:1a00::/32
2604:1a00:1::/48
2604:1a00:2::/48
2604:1a00:7::/48
2604:1a00:8::/48
2604:1a00:9::/48
2604:1a00:a::/48
2604:1a00:b::/48
2604:1a00:d::/48
2604:1a00:e::/48
2604:1a00:f::/48
2604:1a00:10::/48
2604:1a00:12::/48
2604:1a00:13::/48
2604:1a00:14::/48
2604:1a00:15::/48
2604:1a00:16::/48
2604:1a00:18::/48
2604:1a00:19::/48
2604:1a00:1b::/48
2604:1a00:1c::/48
2604:1a00:1e::/48
2604:1a00:20::/48
2604:1a00:21::/48
2604:1a00:22::/48
2604:1a00:23::/48
2604:1a00:26::/48
2604:1a00:2a::/48
2604:1a00:2c::/48
2604:1a00:2d::/48
2604:1a00:2e::/48
2604:1a00:30::/48
2604:1a00:31::/48
2604:1a00:32::/48
2604:1a00:33::/48
2604:1a00:35::/48
2604:1a00:38::/48
2604:1a00:3a::/48
2604:1a00:3b::/48
2604:1a00:3d::/48
2604:1a00:3e::/48
2604:1a00:3f::/48
2604:1a00:40::/48
2604:1a00:41::/48
2604:1a00:47::/48
2604:1a00:48::/48
2604:1a00:49::/48
2604:1a00:4a::/48
2604:1a00:4b::/48
2604:1a00:4c::/48
2604:1a00:4d::/48
2604:1a00:4e::/48
2604:1a00:4f::/48
2604:1a00:50::/48
2604:1a00:52::/48
2604:1a00:53::/48
2604:1a00:54::/48
2604:1a00:55::/48
2604:1a00:56::/48
2604:1a00:58::/48
2604:1a00:5a::/48
2604:1a00:5e::/48
2604:1a00:60::/48
2604:1a00:61::/48
2604:1a00:62::/48
2604:1a00:63::/48
2604:1a00:64::/48
2604:1a00:65::/48
2604:1a00:66::/48
2604:1a00:67::/48
2604:1a00:68::/48
2604:1a00:69::/48
2604:1a00:6a::/48
2604:1a00:6b::/48
2604:1a00:6c::/48
2604:1a00:6d::/48
2604:1a00:70::/48
2604:1a00:71::/48
2604:1a00:72::/48
2604:1a00:73::/48
2604:1a00:74::/48
2604:1a00:75::/48
2604:1a00:76::/48
2604:1a00:77::/48
2604:1a00:78::/48
2604:1a00:79::/48
2604:1a00:7a::/48
2604:1a00:7b::/48
2604:1a00:7d::/48
2604:1a00:7f::/48
2604:1a00:80::/48
2604:1a00:81::/48
2604:1a00:82::/48
2604:1a00:83::/48
2604:1a00:84::/48
2604:1a00:85::/48

Showing the first 100 of 255, in address order. Complete list on RIPEstat

Neighbours

Upstreams (transit or peers) (4)

ASNetworkVisibility
AS6461Zayo Bandwidth213,884
AS47065USC / UFMG PEERING Research Testbed287
AS31769GiGstreem8
AS395748NetSpeed LLC2

Downstreams (customers) (968)

ASNetworkVisibility
AS33132Crown Castle Fiber LLC16,647
AS36352HostPapa1,551
AS398427Markley Network Services, LLC1,340
AS11042NETWORK TRANSIT HOLDINGS LLC1,048
AS3360DXC US Latin America Corporation875
AS36861RWJBarnabas Health, Inc.787
AS11598Cloudsmart715
AS6372DCANet710
AS31942HyperFiber677
AS26793ICS Advanced Technologies623
AS395652-615
AS398875-602
AS20306-591
AS46269-589
AS23410-587
AS25611-584
AS11188-565
AS19272-542
AS27506-542
AS398059-535
AS394548-527
AS6254EG&G, Inc.519
AS18839-517
AS19950-516
AS54576-516
AS395748-516
AS36812-515
AS13990-509
AS15205-509
AS10499-507

The 30 most visible of 968.

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.