Skip to content

Autonomous System

AS1226 · California Department of Technology

Overview

AS1226 is announced on the Internet: RIPE RIS route collectors currently see 32 IPv4 prefixes and no IPv6 prefix originated by this network. Together, its IPv4 prefixes cover 1,037,056 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 3 upstream neighbours (transit providers or peers) and 4 downstream neighbours (customers or networks it carries). Its most visible upstreams are Level 3 Parent, LLC (AS3356), Comcast Cable Communications, LLC (AS33651), and Comcast Cable Communications, LLC (AS33667). AS1226 was assigned by ARIN, and its registration country is United States.

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

Go further

The trace goes to 67.156.0.1, the first address of 67.156.0.0/15. 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 (32 prefixes)

PrefixAddresses
64.112.128.0/198,192
67.156.0.0/15131,072
134.186.0.0/1665,536
134.186.9.0/24256
134.187.0.0/1665,536
146.114.0.0/1665,536
151.143.0.0/1665,536
153.48.0.0/1665,536
153.48.192.0/24256
153.48.240.0/212,048
156.41.0.0/1665,536
156.60.0.0/1665,536
158.96.0.0/1665,536
158.96.29.0/24256
159.145.0.0/1665,536
162.2.0.0/1665,536
165.235.0.0/1665,536
165.235.135.0/24256
169.2.0.0/1665,536
169.3.0.0/1665,536
192.16.175.0/24256
192.56.110.0/24256
198.187.4.0/221,024
198.187.4.0/24256
198.187.5.0/24256
198.187.6.0/24256
198.187.7.0/24256
204.144.113.0/24256
204.193.160.0/198,192
204.235.48.0/212,048
204.235.56.0/221,024
205.225.128.0/1732,768

IPv6 prefixes (none)

None currently seen.

Neighbours

Upstreams (transit or peers) (3)

ASNetworkVisibility
AS3356Level 3 Parent, LLC1,009
AS33651Comcast Cable Communications, LLC420
AS33667Comcast Cable Communications, LLC100

Downstreams (customers) (4)

ASNetworkVisibility
AS1348California Department of Transportation252
AS2894California Department of Water Resources251
AS23281City of Sacramento214
AS401716State Treasurer's Office52

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.