AS927

AS927 is an actively routed autonomous system, though no source meeting this project's operator-attribution bar identifies who runs it. As observed by the RouteViews route collector on 2026-08-20, it originates 2 IPv4 prefixes (an estimated 512 IPv4 addresses) and 0 IPv6 prefixes, with 2 distinct neighboring ASNs seen in the same observation.

Third-party directory and IP-intelligence listings surface a candidate operator name for AS927; it is withheld here because no operator-published source names this ASN. Those listings publish no operator-issued material — they mirror registry data rather than material the operator itself published under its own name.

Because no permitted source binds this AS number to any named operator, operator, as_name, country, and related identity fields are recorded as Unknown here.

Relationship direction comes from a separate dataset on a different day. The CAIDA AS Relationships cache (dataset date 2026-08-01) infers AS174 and AS2914 as transit providers to AS927, with no customers and no settlement-free peers among published neighbours. The same two ASNs also appear as RouteViews's collector-adjacency neighbours on 2026-08-20, though the two observations are separate datasets and are not combined into one claim.

The IANA AS Number registry places AS927 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. Allocation date, RPKI validation posture, exchange-point presence, and peering policy all remain Unknown as of 2026-08. The routing figures above reflect a single collector's snapshot, not a registry-declared allocation size.

Blocklist status

Not listed on the Spamhaus ASN-DROP feed (443 ASN entries in the current feed) as of a 2026-08-24 check — spamhaus.org

Spam reputation

CleanTalk records a 0.00% spam rate for AS927 (0 of 8 detected IP addresses flagged spam-active across 2 monitored networks, 12 total IPs) as of a 2026-08-24 check — cleantalk.org

Community blocklist

Not present in the bountyyfi/bad-asn-list VPN/hosting/malicious-traffic-associated blocklist as of a 2026-08-24 check — github.com/bountyyfi/bad-asn-list

Operator forum activity

No NANOG mailing-list thread referencing AS927 found in the seclists.org/nanog archive as of a 2026-08-24 search — seclists.org/nanog

Operator

Unknown — no material published by the operator themselves names AS927. Third-party directory and IP-intelligence listings surface a candidate operator name; it is withheld here because those sources mirror registry data rather than operator-published material [Unknown]

Country / RIR

Country Unknown — no permitted source names the operator, so no jurisdiction can be asserted [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS927 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no permitted source names the operator [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above for blocklist, spam-reputation, and CVE checks as of a 2026-08-24 search

Network & routing

Network type

Unknown — no operator-published material to describe it [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) AS927

Routing/peering

2 distinct neighboring ASNs observed by RouteViews on 2026-08-20 (full set, not capped): AS174, AS2914. 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): AS927 has no row of its own in the cache, so roles were found by scanning for AS927 as counterparty and inverting the stated role — both AS174 and AS2914 classify AS927 as their customer, making them providers (upstreams) of AS927, with 0 customers and 0 settlement-free peers among published neighbours. This is an inference from observed AS paths, not a disclosed peering agreement, and is a floor, not a census. Peering policy: Unknown [Confirmed for neighbor count; Likely for relationship roles; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS927, the cached registry snapshots/caida-as-rel.csv (rows 174,927,customer and 2914,927,customer)

RPKI

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

Notable usage

Unknown — no operator-published material to draw from [Unknown]

Related ASNs

None found [Unknown]

Related fields

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

Analyst note

Small, actively routed network with two CAIDA-inferred upstream transit providers (AS174, AS2914) and no observed customers or peers, per the RouteViews 2026-08-20 snapshot and the CAIDA dataset dated 2026-08-01. No permitted source identifies who holds AS927; a candidate name found only in IP-intelligence directories does not meet this project's operator-attribution bar and was excluded after checking the candidate's own site directly. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, exchange presence, geo footprint, and abuse contacts are Unknown as of 2026-08. No notable public abuse/security signal found as of a 2026-08-24 search.