AS1608
No prefixes for this AS number were observed in the RouteViews RIB.
Summary
- // analyst note
- Routing figures are a combined observation across both named collectors, not separate per-collector counts.
- // security note
- The combined snapshot observed zero prefixes and zero peers at 2026-11-06 20:00 UTC across route-views2 and route-views6; this limited observation does not establish inactivity or safety.
About this ASN.
AS1608’s operator and purpose are unknown from the supplied evidence, and the combined Route Views snapshot observed zero IPv4 and zero IPv6 prefixes for it at 2026-11-06 20:00 UTC. This is a snapshot result, not evidence that the ASN is inactive or unassigned.
The snapshot combines route-views2 and route-views6 observations. It also records zero observed peers and an empty AS_PATH-neighbour sample. These neighbours, when present, would show routing-path adjacency only; they would not establish commercial peering, upstreams, or customer relationships.
IANA lists AS1608 within resource range 1-1876 as assigned by ARIN. That identifies the allocating RIR for the block; it does not identify an individual assignee, operator, location, or deployment. The supplied material contains no first-party organizational or product evidence linked to this ASN.
For identification, compare observations from additional dates and collectors, then investigate any discovered announcing prefixes through authoritative registry records and first-party documentation that explicitly links the organization to AS1608. Treat the current zero counts as limited to this timestamp and these two collectors. Do not infer safety, malicious use, or legitimacy from the routing absence.
- Routing observation
- Zero IPv4 and IPv6 prefixes and zero peers in the combined snapshot at 2026-11-06 20:00 UTC across route-views2 and route-views6.
- Identity
- Operator and ASN purpose are Unknown in the supplied evidence.
- Triage
- The zero-route observation is limited to this timestamp and collector set; it does not establish inactivity or safety.
- Operator
- Unknown [Unknown]
- AS name
- Unknown [Unknown]
- Country
- Unknown [Unknown]
- Website
- Unknown [Unknown]
- Allocated date
- Unknown [Unknown]
Network & routing
- Network type
- Unknown [Unknown]
- AS rank
- Unknown [Unknown]
- Customer cone size
- Unknown [Unknown]
- IX presence
- Unknown [Unknown]
- Peering policy
- Unknown [Unknown]
- RPKI status
- Unknown [Unknown]
- Observation scope
- combined RouteViews snapshot at 2026-11-06T20:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
- ASN
- 1608 [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
- Organization status
- Unknown [Unknown]
- Assignment class
- Unknown [Unknown]
- Last updated
- Unknown [Unknown]
- IPv4 prefixes
- 0 observed [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
- IPv4 address estimate
- 0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
- IPv6 prefixes
- 0 observed [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
- Peer count
- 0 observed [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
- AS_PATH neighbours sample
- None observed [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2