AS926

AS926 shows no originated IPv4 or IPv6 prefixes in the RouteViews route-collector snapshot dated 2026-08-20, and no operator-published material identifies who holds the registration as of an August 2026 search — this is a dormant or unrouted ASN, not an active carrier or enterprise network with a confirmable identity.

A grep of the RouteViews cache anchored on AS926 returned zero rows: the collector observed no prefix, IPv4 or IPv6, originated by this ASN at that instant. This is reported as a genuine none-observed finding, not a failed lookup — scoped strictly to "as observed by RouteViews on 2026-08-20," since a snapshot cannot confirm the ASN has never routed anything.

A broad web search for the exact string "AS926" surfaced no networking-related identification: hits were an unrelated strut-brace part number, a digital tachometer listing, and an Alaska Airlines flight number that happens to share the digits. The only ASN-adjacent hits were third-party directories and registry mirrors — an IRR AS-SET, an autnums mirror, a route-report aggregator, and a PeeringDB entry that in fact resolves to a different ASN — none of which is material the operator itself published, so none of them binds an identity to AS926 under the operator-official test.

The IANA AS Number registry places AS926 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row for AS926 in either column checked, so it has no CAIDA-inferred provider, customer, or peer relationship among published neighbours — unclassified, not zero as a fact about the network. Allocation date, RPKI status, IX presence, and abuse contacts remain Unknown.

Routing exposure

none observed — AS926 originates no prefixes in the 2026-08-20 RouteViews snapshot, so it presents no observable traffic surface for abuse reporting.

Blocklist status

Unknown — direct queries to check.spamhaus.org/query/asn/926 and Cisco Talos's reputation lookup both returned HTTP 403 Forbidden as of an August 2026 check, so neither service's verdict could be retrieved.

General abuse signal

none found — search-engine queries combining "AS926" with abuse, spam, malware, botnet, hijack, AbuseIPDB, VirusTotal, and ThreatFox terms returned no relevant results as of an August 2026 search.

Community mentions

none found — no NANOG mailing-list or seclists.org discussion naming AS926 was located as of an August 2026 search.

CVE / malware

no CVE, malware, or botnet command-and-control association naming AS926 found as of an August 2026 search.

Operator

Unknown — no operator-published material (site, IR page, peering policy, looking-glass, or mailing-list post under an operator's own name) identifying the holder of AS926 was found as of an August 2026 search [Unknown]

Country / RIR

Country Unknown — no operator-published material names a jurisdiction [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS926 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no operator-published material identifies a holding organization or its operating status [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above; no abuse, blocklist, or CVE association found as of an August 2026 search, though Spamhaus and Talos lookups specifically returned HTTP 403 rather than a clean negative

Network & routing

Network type

Unknown — no operator-published material identifies a network type [Unknown]

Size

0 IPv4 prefixes and 0 IPv6 prefixes originated, per a grep of the RouteViews cache anchored on AS926, which returned zero rows at the 2026-08-20 dump [Confirmed — none-observed] — the RouteViews BGP routing data (CC BY 4.0) AS926 (no row)

Routing/peering

0 distinct neighboring ASNs observed by RouteViews on 2026-08-20 (no row in the cache). The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row for AS926 in either the provider-side or customer-side column, so it is unclassified among published neighbours — a floor over published ASNs only, not evidence of zero relationships as a fact about the network [Confirmed for the absence of a cache row; not a census] — the RouteViews BGP routing data (CC BY 4.0) AS926, the cached registry snapshots/caida-as-rel.csv AS926 (no row either column)

RPKI

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

Notable usage

Unknown — no operator-published material describes any use of this ASN [Unknown]

Related ASNs

None found [Unknown]

Related fields

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

Analyst note

AS926 shows no originated prefixes in the 2026-08-20 RouteViews snapshot and no CAIDA-classified relationship in the 2026-08-01 dataset — either dormant, unrouted, or observed by neither collector at that instant. No operator-published material was found identifying who holds the registration, so operator, country, network type, and related identity fields all stay Unknown per the operator-official test rather than being inferred from directory mirrors. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown as of 2026-08.