AS930

AS930 is an actively routed autonomous system originating a small IPv4-only network — 2 prefixes, an estimated 512 addresses — as observed by the RouteViews route collector on 2026-08-20. This is a small standalone network, not a dormant or unrouted registration, but no operator-published source located during research names the entity that holds this AS number.

RouteViews recorded 3 distinct neighboring ASNs at that same observation: AS174, AS6461, and AS7459. This is undirected AS-path adjacency, not a directional relationship classification, and the count is the full observed set, not a truncated sample against the dataset's 32-entry cap.

Relationship direction comes from a separate dataset on a different day. The CAIDA AS Relationships cache (dataset date 2026-08-01) infers AS174 as a transit provider to AS930, recovered by inverting a customer-side entry naming AS930 as AS174's customer; no customer or settlement-free peer relationship is inferred for AS930 in this dataset. This is an algorithmic inference from observed paths, not a disclosed peering or transit agreement.

The IANA AS Number registry places AS930 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. IANA states no finer assignment class for this range beyond the RIR delegation. Allocation date, RPKI validation posture, IX presence, and abuse contact are Unknown; the routing figures above reflect a single collector's snapshot, not a registry-declared allocation record.

A systematic search for operator-published material — general web search, NANOG and RIPE mailing-list archives, IRR/RADB references, and phrase searches for operator self-identification — found no peering-policy page, network/IR page, looking glass, or mailing-list post published under any party's own name that names AS930. The only network-related references located were on third-party directory and IP-intelligence aggregator sites, a source class excluded from identity determination here; operator, as_name, website, network type, org status, country, and geo footprint are therefore Unknown as a matter of sourced fact, not a gap awaiting further research.

Community reporting

No mentions of AS930 found in a NANOG mailing-list archive search-index check as of August 2026; this is a search-index check rather than a full-text archive search, so the absence carries lower confidence than the direct Spamhaus list check above.

Exposure

A small, two-prefix network with a single CAIDA-inferred upstream (AS174); no ASN-wide abuse or threat-feed signal found as of an August 2026 search, though this reflects search coverage rather than a guaranteed clean record.

Operator identity

No permitted source confirms who operates AS930, so no operator-specific incident history (breaches, ransomware, or otherwise) could be checked against a named organization.

Operator

Unknown — a systematic search (general web, NANOG/RIPE mailing-list archives, IRR/RADB references, and operator self-identification phrase searches) found no operator-published material — own site, peering-policy page, IR/network page, looking glass, or mailing-list post under the operator's own name — that names AS930. Only third-party directory/IP-intelligence aggregator sites associate a name with this ASN, and those are excluded from identity determination here

[Unknown] — (no permitted source found)

Country / RIR

Country Unknown — no operator-published source identifies a physical location or registrant country for AS930 [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS930 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no operator-published source confirms the operating organization's legal or operational status [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above; not listed on the Spamhaus ASN-DROP list as of 2026-08-25, and no CVE, malware, or NANOG-archive mention found as of an August 2026 search

Network & routing

Network type

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

Size

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

Routing/peering

3 distinct neighboring ASNs observed by RouteViews on 2026-08-20 — AS174, AS6461, AS7459 — the full observed set, under the 32-entry sample cap; this is undirected AS-path adjacency, not a customer/upstream/peer classification. Relationship direction comes separately from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA), which infers AS174 as a transit provider to AS930 (recovered by inverting a column-2 entry naming AS930 as AS174's customer); no customer or settlement-free peer relationship is inferred. This is a CAIDA algorithmic inference from observed AS paths, not a disclosed peering agreement. Peering policy: Unknown — no operator-published technical peering-policy page found [Confirmed for the neighbor count; Inferred for the upstream relationship; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS930, the cached registry snapshots/caida-as-rel.csv 174,930,customer

RPKI

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

Notable usage

Unknown — no operator-published source describes how this network is used [Unknown]

Related ASNs

None identified [Unknown]

Related fields

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

Analyst note

A small, actively routed ASN: RouteViews observed 2 IPv4 / 0 IPv6 prefixes and 3 neighboring ASNs (AS174, AS6461, AS7459) on 2026-08-20; this is a single collector snapshot, not a registry-declared allocation size. AS174 is a CAIDA-inferred upstream transit provider 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); no customer or settlement-free peer relationship is inferred for AS930. RIR is ARIN, from the IANA AS Number registry range 1-1876. No operator-published source identifies the holder, network type, country, or notable usage; those fields are Unknown, not a gap awaiting further research. Allocation date, RPKI status, IX presence, and abuse contacts are also Unknown.