AS929

AS929 is a small, actively routed autonomous system: RouteViews observed it originating 3 IPv4 prefixes and 0 IPv6 prefixes on 2026-08-20 — an estimated 3,072 IPv4 addresses — with exactly one neighboring ASN recorded, AS41378. No operator-published source was found that names AS929, so its holder remains formally unconfirmed here.

An exhaustive search for operator-official material — peering-policy pages, network-operations or investor-relations pages, a looking glass, IRR/AS-SET or routing-config repositories, and NANOG/RIPE mailing-list posts — turned up nothing that names AS929 directly. One candidate operator homepage was read in full and does not mention AS929 anywhere; a second domain associated with AS929 only in third-party directory listings returned a server error and has no independently indexed content.

Per this project's identity rule, only material an operator publishes under its own name can bind an ASN to an organization — a directory or whois-mirror listing does not qualify, however many of them agree, because they typically republish the same underlying record. Third-party listings did surface a candidate operator name for AS929, but it is withheld here: operator, as_name, country, geo_footprint, network_type, org_status, and website all stay Unknown.

Relationship direction comes from a separate dataset. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no classified provider, customer, or peer relationship for AS929 in either direction — checked as both source and counterparty — so its posture is unclassified, not zero and not peer. The IANA AS Number registry places AS929 in the 1-1876 range recorded as "Assigned by ARIN," so ARIN administers this allocation; the registry states no finer per-ASN assignment class.

Allocation date, RPKI validation posture, IX presence, peering policy, AS rank, and customer cone size are all Unknown as of 2026-08. The routing figures above reflect a single RouteViews collector snapshot at one instant, not a registry-declared allocation size or a broader claim about what this network announces.

Blocklist status

AS929 does not appear in the brianhama/bad-asn-list community blocklist, checked directly against the raw CSV as of August 2026; a second list (C0nw0nk/ASN-BlackList) could not be checked because its raw file returned a 404, so status there is Unknown — raw.githubusercontent.com/brianhama/bad-asn-list/master/bad-asn-list.csv.

CVE / malware / NANOG

No CVE, malware/botnet association, or NANOG mailing-list thread naming AS929 specifically (hijacks, route leaks, peering disputes, abuse) was found as of an August 2026 search.

Relationship posture

The CAIDA AS Relationships dataset (dataset date 2026-08-01) carries no classified provider, customer, or peer relationship for AS929 in either direction, checked as both source and counterparty — unclassified, not confirmed isolation.

Name-collision caution

IP-reputation lookups touching this ASN frequently surface abuse data belonging to a different, numerically distinct ASN, AS41378 — AS929's sole RouteViews-observed neighbor; AS41378's documented abuse history should not be attributed to AS929 — cleantalk.org/blacklists/as41378/37.123.192.0/21.

Operator

Unknown — no operator-published source (peering-policy page, network-operations/IR page, looking glass, IRR/AS-SET or routing-config repository, NANOG/RIPE mailing-list post) names AS929 as of an August 2026 search; third-party directory/whois-mirror listings are not treated as binding [Unknown]

Country / RIR

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

Allocated

Unknown [Unknown]

Org status

Unknown — no operator-published source confirms an organization behind AS929 [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

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

Network & routing

Network type

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

Size

3 IPv4 prefixes and 0 IPv6 prefixes originated; an estimated 3,072 IPv4 addresses, as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS929

Routing/peering

Exactly 1 neighboring ASN observed by RouteViews on 2026-08-20 (AS41378, an ordinary 16-bit ASN outside the reserved/private ranges); this is undirected AS-path adjacency, not a customer/upstream/peer classification. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no classified provider, customer, or peer relationship for AS929 in either direction, checked as both source and counterparty — its posture is unclassified, not zero and not peer. Peering policy: Unknown [Confirmed for the neighbor count and unclassified status; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS929, the cached registry snapshots/caida-as-rel.csv

RPKI

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

Notable usage

Unknown — no operator-published source describes this network's use [Unknown]

Related ASNs

AS41378 — the sole neighboring ASN observed by RouteViews on 2026-08-20, and the subject of a name-collision caution in the Security section above [Confirmed for the routing adjacency] — the RouteViews BGP routing data (CC BY 4.0) AS929

Related fields

AS rank, customer cone size, RPKI status, IX presence, and MANRS membership are all Unknown [Unknown]

Analyst note

Small, actively routed ASN observed by a single RouteViews snapshot (2026-08-20): 3 IPv4 prefixes, 0 IPv6 prefixes, roughly 3,072 IPv4 addresses, and exactly one neighboring ASN (AS41378). No operator-published source names AS929's holder despite an exhaustive search of peering-policy pages, NOC/IR pages, a looking glass, IRR/AS-SET repositories, and NANOG/RIPE mailing lists; third-party directory/whois-mirror listings surfaced a candidate name but are not binding under this project's identity rule, so operator, as_name, and country stay Unknown. RIR is ARIN, from the IANA AS Number registry range 1-1876. CAIDA (dataset date 2026-08-01, a separate observation from the RouteViews snapshot) carries no classified relationship for AS929. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown as of 2026-08.