Autonomous system detail

AS1096

Announced

AS1096 announces 1 IPv4 and 0 IPv6 prefixes and peers with 1 other networks.

Summary

// analyst note
One combined observation across route-views2 and route-views6 at 2026-11-03T14:00:00.000Z; AS174 is an observed AS_PATH neighbour, not a verified peer or upstream.
IPv4 prefixes
1
~256 addresses
IPv6 prefixes
0
—
Peer networks
1
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Low  ·  3 sources  ·  How this page is checked

AS1096 has no identified operator in the supplied evidence. In the combined Route Views observation at 2026-11-03 14:00 UTC, it had one IPv4 prefix, zero IPv6 prefixes, and one observed AS_PATH neighbour: AS174. These observations come from route-views2 and route-views6 together; they do not establish commercial peering, an upstream relationship, or the ASN’s current operator.

The single IPv4 prefix represents an estimated 256 addresses in this snapshot. The zero IPv6 count means no IPv6 prefix was observed in this combined snapshot, not that the ASN is inactive or has no IPv6 allocation. IANA identifies ASN 1096 as part of resource range 1–1876, assigned by ARIN; this identifies the allocating RIR, not an individual assignment or deployed network.

For triage, compare the observed route and AS_PATH with a fresh routing view and inspect the announced prefix’s origin and route history before attributing it to an organization. Treat AS174 only as an observed path neighbour. The supplied evidence does not identify a website, country, network type, or security status, so those cannot support attribution or a safety judgment.

Routing snapshot
One IPv4 prefix and zero IPv6 prefixes observed at 2026-11-03 14:00 UTC across route-views2 and route-views6 combined.
Observed neighbour
AS174 appears as an AS_PATH neighbour; this does not establish an upstream or commercial peer.
Triage
Check the specific announced prefix and its route history before making an attribution; operator and security status are unknown from supplied evidence.
Operator
Unknown [Unknown] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Observation scope
combined RouteViews snapshot at 2026-11-03T14:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
ASN
1096 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Allocating RIR
ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
IPv4 prefixes observed
1 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
IPv4 address estimate
256 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
IPv6 prefixes observed
0 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
Observed AS_PATH neighbour
AS174 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
[ 02 ] — Announced prefixes

What this network routes.

1 prefixes total · as observed by RouteViews at 2026-11-06 · one collector view, not a global census
// IPv4 prefixes1
  1. 38.97.2.0/24/24
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

1 observed neighbour
// Notable connections1 of 1 observed

Neighbours observed by RouteViews at 2026-11-06, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.

ASNOperatorRole
AS174 Cogent Communications, LLC —
Neighbours observed via public BGP collectors; not a complete peering list.