AS897

AS897 is a small, actively routed autonomous system whose operator has no permitted source naming it as of August 2026. As observed by RouteViews at 2026-08-20T00:00:00Z, it originates 3 IPv4 prefixes (an estimated 768 addresses) and 5 IPv6 prefixes, with 6 distinct neighboring ASNs seen in the same snapshot — a footprint consistent with one organization's own connectivity, not a carrier or hosting backbone.

No operator-published material identifying AS897 was found. The only material that names a company in connection with this ASN consists of whois-panel mirrors of the underlying registry record, and this entry does not treat those mirrors as a permitted binding for operator identity. Operator, country, network type, org status, and prior-registration history are therefore reported as Unknown rather than asserted from that material.

CAIDA's AS Relationships dataset (dataset date 2026-08-01) supplies an inferred direction for four of the six observed neighbors: AS174, AS3356, and AS16509 are each classified as a provider to AS897, with AS897 sitting as the customer, and AS6939 is classified as a settlement-free peer among published neighbours. AS6461 and AS58511 carry no row in that dataset and stay unclassified rather than guessed at.

These relationship roles are algorithmic inferences drawn from observed AS paths on CAIDA's own monthly cadence, not disclosed peering agreements or confirmed commercial contracts, and they are dated separately from the same-day RouteViews snapshot above.

Several fields a routing-registry lookup would normally supply remain Unknown as of 2026-08: the ASN's original allocation date, RPKI validation posture, and exchange-point presence. The routing figures above reflect a single collector snapshot, not a registry-declared allocation size, and should be read with that scope in mind.

Abuse/threat feeds

No listing, hijack, route-leak, or malware-hosting report naming AS897 found across Spamhaus, abuse.ch (URLhaus/ThreatFox/MalwareBazaar), and Cisco Talos Intelligence as of an August 2026 search — spamhaus.org, abuse.ch, blog.talosintelligence.com.

Community signal

No NANOG mailing-list thread, documented outage, or abuse complaint naming AS897 found as of an August 2026 search — archive.nanog.org, mailman.nanog.org.

CVE / malware

No CVE or malware/botnet command-and-control association naming AS897 found as of an August 2026 search.

Context

The absence of abuse signal is consistent with a small, single-organization network rather than a transit or hosting provider carrying third-party traffic.

Operator

Unknown — no operator-published source names AS897; the only material connecting this ASN to a company consists of whois-panel mirrors of the underlying registry record, not treated here as a permitted binding [Unknown]

Country / RIR

RIR = ARIN, per the IANA AS Numbers registry range row covering AS897 [Confirmed] — the IANA Autonomous System Number registry 1-1876. Country: Unknown — no operator-published source states a location [Unknown]

Allocated

Unknown [Unknown]

Org status

Unknown — no operator-published source confirms an operating entity for this ASN [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above; no abuse, blocklist, hijack, or malware association found as of an August 2026 search

Network & routing

Network type

Unknown — no operator-published source describes this ASN's network or peering purpose [Unknown]

Size

3 IPv4 prefixes and 5 IPv6 prefixes originated; an estimated 768 IPv4 addresses, as observed by RouteViews at 2026-08-20T00:00:00Z [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS897

Routing/peering

6 distinct neighboring ASNs observed by RouteViews at 2026-08-20T00:00:00Z (full observed set, below the 32-entry sample cap): AS174, AS3356, AS6461, AS6939, AS16509, AS58511; this is undirected AS-path adjacency on its own. The CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA) infers AS174, AS3356, and AS16509 as transit providers to AS897 (AS897 is the customer) and AS6939 as a settlement-free peer among published neighbours; AS6461 and AS58511 carry no row in that dataset and stay unclassified, not peers. These are inferences drawn from observed paths, not disclosed peering agreements [Confirmed for the neighbor count and routing figures; Likely for relationship roles] — the RouteViews BGP routing data (CC BY 4.0) AS897, the cached registry snapshots/caida-as-rel.csv AS897

RPKI

Unknown — an unevaluated status, not a report of an absent or invalid ROA [Unknown]

Notable usage

Unknown — no operator-published source describes what traffic runs over this ASN [Unknown]

Related ASNs

Unknown — no permitted source establishes a prior or related registration for this ASN [Unknown]

Related fields

AS rank, customer cone size, and MANRS membership are all Unknown [Unknown]

Analyst note

Small, actively routed ASN with no operator identity confirmed by a permitted source as of August 2026. Routing figures reflect a single RouteViews observation (2026-08-20T00:00:00Z), not a registry-declared allocation size. CAIDA (dataset date 2026-08-01) infers AS174, AS3356, and AS16509 as upstream providers and AS6939 as a settlement-free peer among the six observed neighbours, stated as an inference rather than a disclosed agreement; AS6461 and AS58511 remain unclassified. No public abuse or community-incident signal found as of an August 2026 search. Allocation date, country, network type, RPKI status, and exchange presence are Unknown.