AS921
No prefixes for this AS number were observed in the RouteViews RIB.
Summary
- // analyst note
- Registered ARIN ASN (IANA 1-1876 block, "Assigned by ARIN") with no observed routing activity: RouteViews saw 0 IPv4/IPv6 prefixes and 0 neighboring ASNs on 2026-08-20 across route-views2 and route-views6. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row for AS921 in either column, so relationships are unclassified rather than a zero floor. No permitted (operator-published) source names an operator, as_name, country, or website for this ASN. Not present on Spamhaus ASN-DROP as of 2026-08-23; no NANOG or general abuse/threat-intel coverage found as of an August 2026 search. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown.
- // security note
- NEUTRAL/DATED: AS921 is not present in the Spamhaus ASN-DROP list as of 2026-08-23 (checked asndrop.txt and asndrop.json).
About this ASN.
AS921 is a registered autonomous system administered by ARIN that currently originates zero prefixes in the routing table, making it a dormant or not-yet-routed registration rather than an active carrier or enterprise network.
As observed by RouteViews at its 2026-08-20 dump, neither the route-views2 nor route-views6 collector recorded any IPv4 or IPv6 prefix originated by AS921, and no neighboring ASN was observed adjacent to it. This is a real, sourced zero, not a failed lookup, and it is scoped to that single collector instant.
No permitted source identifies AS921's operator. Forward searches for peering-policy pages, looking-glass entries, and NANOG or RIPE list posts naming AS921 under an operator's own name returned nothing; the only hits were unrelated (a flight number, a course code, a bill number) or third-party directories, which do not establish operator identity under this entry's binding test. Operator, as_name, country, network type, and website therefore stay Unknown.
The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row naming AS921 as either a column-1 target or a column-2 counterparty, so its relationships are unclassified rather than a zero floor of providers, customers, or peers — CAIDA simply has no published-neighbour data for this ASN.
The IANA AS Number registry places AS921 within the 1-1876 range recorded as "Assigned by ARIN," so ARIN is the administering RIR. IANA's per-block table gives no registration date or reference for this range, and allocation date, RPKI validation posture, IX presence, and abuse contacts all remain Unknown.
- Blocklist status
- AS921 is not present in the Spamhaus ASN-DROP list as of 2026-08-23 (checked both asndrop.txt and asndrop.json, which span ASN values 245 to 219,502 with none in the 900-950 range) — spamhaus.org.
- Community/abuse mentions
- No NANOG mailing-list post and no general abuse or threat-intel coverage naming AS921 was found via web search as of 2026-08-23 — seclists.org/nanog.
- CVE / malware
- No CVE, malware, or botnet command-and-control association naming AS921 found as of an August 2026 search.
- Routing hygiene
- No hijack or route-leak incident found for AS921; the ASN currently announces no prefixes at all, so there is nothing in the current table to leak or hijack.
- Operator
- Unknown — no operator-published material (own domain, IR/investor page, peering policy, looking glass, or a NANOG/RIPE list post under an operator's own name) names AS921's holder; third-party directories do not qualify under the binding test [Unknown]
- Country / RIR
- Country Unknown — no operator-published material establishes a jurisdiction. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS921 as "Assigned by ARIN" [Confirmed for RIR; Unknown for country] — the IANA Autonomous System Number registry 1-1876
- Allocated
- Unknown [Unknown]
- Org status
- Unknown — no operator-published material identifies a registrant organization or corporate status [Unknown]
- Contacts
- Unknown [Unknown]
Security/abuse context (NEUTRAL, DATED)
see the Security section above; not present in Spamhaus ASN-DROP as of 2026-08-23, and no NANOG or general abuse/threat-intel coverage found as of an August 2026 search
Network & routing
- Network type
- Unknown — no operator-published material identifies this network's purpose [Unknown]
- Size
- 0 IPv4 prefixes and 0 IPv6 prefixes originated; no address estimate, as observed by RouteViews on 2026-08-20 across both the route-views2 and route-views6 collectors [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS921 (anchored grep ^921, — no row returned)
- Routing/peering
- 0 neighboring ASNs observed by RouteViews on 2026-08-20. No relationship data in the CAIDA AS Relationships cache (dataset date 2026-08-01) — AS921 appears in neither column 1 nor column 2, so relationships are unclassified, not a zero floor of providers, customers, or peers. Peering policy: Unknown [Confirmed for the RouteViews null result; unclassified, not Confirmed-zero, for relationships] — the RouteViews BGP routing data (CC BY 4.0) AS921, the cached registry snapshots/caida-as-rel.csv AS921
- RPKI
- Unknown — an unevaluated status, not a report of an absent or invalid ROA [Unknown]
- Notable usage
- Unknown — no operator-published material found [Unknown]
- Related ASNs
- Unknown — none identified [Unknown]
- Related fields
- AS rank, customer cone size, and MANRS membership are all Unknown [Unknown]
- Analyst note
- Registered ARIN ASN (IANA 1-1876 block) with no observed routing activity — 0 IPv4/IPv6 prefixes and 0 neighboring ASNs in the RouteViews 2026-08-20 snapshot — and no CAIDA-classified relationships as of the 2026-08-01 dataset (unclassified, not a zero floor). No permitted source names an operator. Not present on Spamhaus ASN-DROP as of 2026-08-23, and no NANOG or general abuse coverage found. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown.