AS896

AS896 is a small but actively routed autonomous system: RouteViews observed it originating 4 IPv4 prefixes and 0 IPv6 prefixes on 2026-08-20, an estimated 1,024 IPv4 addresses in total. That places it well outside the dormant/reclaimed category, even though its operator has not been confirmed to a verifiable legal entity.

RouteViews recorded exactly two neighboring ASNs at the same snapshot, 2026-08-20T00:00:00Z — AS174 and AS211428 — the full observed set rather than a capped sample. Relationship roles come separately from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA), which carries exactly one classified relationship touching AS896: AS174 as an inferred transit provider. That is a CAIDA inference drawn from observed AS paths, not a disclosed peering agreement. AS211428 is not classified by CAIDA and is not asserted as a peer.

AS896's RIR is ARIN, per the IANA AS Numbers registry. Allocation date, RPKI status, exchange presence, and abuse contacts are likewise Unknown as of 2026-08: no permitted source supplied them for this entry, and no operator commentary or outage report surfaced in NANOG archives or general community search.

Blocklist status

Not listed on the Spamhaus ASN-DROP feed, checked live against the current JSON feed on 2026-08-19/20 — spamhaus.org/drop/asndrop.json.

Threat-feed check

No indexed reports referencing AS896 or its announced prefixes found in abuse.ch's URLhaus, ThreatFox, or MalwareBazaar feeds, or in Cisco Talos's reputation center, as of an August 2026 search — urlhaus.abuse.ch, threatfox.abuse.ch, bazaar.abuse.ch, talosintelligence.com.

CVE / malware

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

Community signal

No outage reports or operator commentary found in NANOG mailing-list archives or general community search as of August 2026; the absence reflects limited public visibility for a small ASN, not a confirmed clean history.

Operator

Unknown — no permitted source binds AS896 to an operator [Unknown]

Country / RIR

RIR = ARIN, per the IANA AS Numbers registry range row covering AS896 [Confirmed] — the IANA Autonomous System Number registry 1-1876. Country: Unknown — no confirmed first-party registrant location [Unknown]

Allocated

Unknown [Unknown]

Org status

Unknown — no permitted source establishes an operating organization for this ASN [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above for blocklist, threat-feed, and CVE checks as of an August 2026 search

Network & routing

Network type

Unknown — no permitted source describes this ASN's network type [Unknown]

Size

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

Routing/peering

2 distinct neighboring ASNs observed by RouteViews at 2026-08-20T00:00:00Z — AS174 and AS211428 — the full observed set, not a capped sample; this is undirected AS-path adjacency and carries no direction on its own. Relationship roles come separately from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA), which carries exactly one classified relationship touching AS896: AS174 as an inferred transit provider (174,896,customer) — a CAIDA inference from observed AS paths, not a disclosed peering agreement. AS211428 is not classified by CAIDA and is not asserted as a peer. Peering policy: Unknown — no first-party peering-policy page located [Confirmed for the neighbor count/identities and the AS174 upstream inference; Unknown for AS211428's relationship role and for peering policy] — the RouteViews BGP routing data (CC BY 4.0) AS896, the cached registry snapshots/caida-as-rel.csv AS896

RPKI

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

Notable usage

Unknown — no customer names, traffic figures, or usage examples found [Unknown]

Related ASNs

None confirmed [Unknown]

Related fields

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

Analyst note

Small, actively routed ASN — 4 IPv4 / 0 IPv6 prefixes and 2 observed neighbors per RouteViews at 2026-08-20T00:00:00Z — not a dormant registration. RIR is ARIN per the IANA AS Numbers registry. CAIDA's AS Relationships cache (dataset date 2026-08-01) infers AS174 as a transit provider to AS896; AS211428 is unclassified. No public abuse or security signal found as of an August 2026 search. Allocation date, RPKI status, and exchange presence are Unknown for lack of a permitted source.