AS922

AS922 is an actively routed autonomous system that originates a small amount of address space; no operator-published material identifies who runs it, so this entry cannot name a holder. As observed by the RouteViews route collector on 2026-08-20, AS922 originates 38 IPv4 prefixes and 19 IPv6 prefixes — an estimated 15,616 IPv4 addresses — with 2 distinct neighboring ASNs seen in the same observation, confirming a live, multihomed network rather than an unrouted or reserved registration.

A dedicated operator-identity search (own-domain pages, investor/IR material, peering-policy pages, looking-glass output, and NANOG/RIPE mailing-list posts under an operator's own name) found nothing naming AS922. Two candidate operator names surface only in third-party directory and mirror listings that republish the same registry record one hop out and conflict with each other, so neither is asserted here.

Relationship direction comes from a separate dataset on a different day. The CAIDA AS Relationships cache (dataset date 2026-08-01) does not list AS922 as a published target in its own right, but two rows name it as the customer side of a relationship with AS14618 and AS16509; inverted per the resolver's convention, that makes both ASNs inferred transit providers to AS922, with no inferred customers or settlement-free peers among published neighbours.

Those are inferences drawn from observed paths, not disclosed peering agreements, and the counts are a floor rather than a census: a pair CAIDA does not classify is unclassified, never a peer. The IANA AS Number registry places AS922 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN.

Several fields a routing-registry lookup would normally supply stay Unknown as of 2026-08: the ASN's operator, country, original allocation date, RPKI validation posture, exchange-point presence, and peering policy. The routing figures above reflect a single collector's snapshot, not a registry-declared allocation size, and should not be read as a claim about what the network announces at other times.

BGP integrity

No BGP hijack or route-leak incident naming AS922 was found as of an August 2026 search — nanog.org.

Blocklist status

No ASN-wide DNSBL/blocklist listing (Spamhaus SBL/XBL/ASN-DROP) was found for AS922 as of an August 2026 search; Spamhaus's own interactive checker was not queried directly in this pass, so this is a search-coverage negative, not a confirmed clean result — spamhaus.org.

Threat-feed classification

No GreyNoise mass-scanning classification was found for AS922 as of an August 2026 search; abuse.ch's URLhaus ASN page for AS922 returned an HTTP 403 during this pass and could not be checked — greynoise.io, urlhaus.abuse.ch.

Community visibility

No NANOG mailing-list thread or Reddit discussion naming AS922 was found as of an August 2026 search — seclists.org/nanog.

Operator identity

No operator-published material identifies who runs AS922, so no operator-specific abuse or reputation history can be attributed to this ASN entry; candidate names appearing only in mirror directories are not confirmed and are not used here.

Operator

Unknown — no operator-published material (own domain, IR/investor pages, peering-policy page, looking glass, or NANOG/RIPE list post under the operator's own name) names AS922; directory/mirror listings surface two conflicting candidate names but establish no provenance [Unknown]

Country / RIR

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

Allocated

Unknown [Unknown]

Org status

Unknown — no operator is identified, so no confirmable corporate status [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above for ASN-level BGP-integrity, blocklist, threat-feed, and community-visibility checks as of an August 2026 search

Network & routing

Network type

Unknown — no operator-published material describes this network's purpose [Unknown]

Size

38 IPv4 prefixes and 19 IPv6 prefixes originated; an estimated 15,616 IPv4 addresses, as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS922

Routing/peering

2 distinct neighboring ASNs observed by RouteViews on 2026-08-20 — the full list, not a capped sample: AS14618, AS16509. This is undirected AS-path adjacency, not a customer/upstream/peer classification. Relationship roles come separately from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA): AS922 has no row of its own as a column-1 target, but appears as the customer side on two rows ("14618,922,customer" and "16509,922,customer"), which invert to AS14618 and AS16509 both being inferred providers of AS922 — 2 providers, 0 customers, 0 peers among published neighbours. Peering policy: Unknown [Confirmed for neighbor count; Inferred for relationship roles; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS922, the cached registry snapshots/caida-as-rel.csv (rows 14618,922,customer and 16509,922,customer)

RPKI

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

Notable usage

Unknown — no operator-published material found describing this network's use [Unknown]

Related ASNs

Unknown — no related-ASN association found via a permitted source [Unknown]

Related fields

AS rank, customer cone size, IX presence, and peering policy are all Unknown [Unknown]

Analyst note

Actively routed but small ASN — RouteViews observed 38 IPv4 / 19 IPv6 prefixes and 2 neighboring ASNs on 2026-08-20; this is a single collector snapshot, not a registry-declared allocation size. No operator-published material names AS922, so operator, as_name, country, network_type, org_status, and website all stay Unknown despite candidate names appearing in third-party mirror directories that conflict with each other and establish no provenance. AS14618 and AS16509 are CAIDA-inferred transit providers to AS922 among published neighbours (CAIDA AS Relationships, dataset date 2026-08-01 — a separate observation from the RouteViews snapshot above; an inference from observed AS paths, not a disclosed peering agreement), with no inferred customers or peers. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, exchange presence, peering policy, and abuse contacts are Unknown as of 2026-08.