AS918

AS918 is a live but minimal ASN: as observed by RouteViews at the 2026-08-20 dump, it originates exactly 1 IPv4 prefix (a /24, an estimated 256 addresses) and 1 IPv6 prefix, with a single neighboring ASN in view. No operator-published source names who holds it.

An exhaustive August 2026 search for operator-self-published material — peering-policy pages, looking-glass tools, NANOG/RIPE mailing-list posts under an operator's own name — found nothing verifiable naming AS918. Third-party directories and IP-intelligence aggregators surfaced mentions, but those do not establish provenance and are excluded per sourcing policy.

Two candidate operator domains suggested by directory snippets both failed TLS certificate validation on inspection and could not be read as genuine operator material, so neither is cited. Four NANOG archive links matched by a keyword search were individually checked and none actually mention AS918 — false-positive matches on unrelated Sprint/UUNET/AT&T-XO threads.

RouteViews' single neighboring ASN for AS918 is AS3399, an ordinary registered ASN outside any reserved or private range, so no leak or misconfiguration flag applies. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries zero rows touching AS918 in either the origin or counterparty column — unclassified among published neighbours, not a confirmed absence of upstream or peer relationships.

The IANA AS Number registry places AS918 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN; the registry's own allocation-date column for that range is blank. Allocation date, RPKI validation posture, IX presence, and abuse contacts are all Unknown as of 2026-08 — no permitted source supplies them.

Abuse signal

No notable public abuse signal found for AS918 as of an August 2026 search across general web search and reputable abuse/threat sources.

NANOG archive

A MARC archive search of the NANOG mailing list for "AS918" returned zero hits as of an August 2026 check — marc.info.

Blocklist status

Spamhaus's dedicated ASN-check page (check.spamhaus.org) returned HTTP 403 on an August 2026 attempt; general Spamhaus site search surfaced no AS918-specific listing, so DROP/ASN-DROP status is Unknown rather than confirmed-clean.

Abuse database

AbuseIPDB's ASN report page for AS918 returned HTTP 404 as of an August 2026 attempt, so no AbuseIPDB-sourced statistic could be confirmed.

CVE / malware

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

Community visibility

No mentions of AS918 found in accessible NANOG archives or networking-focused Reddit communities as of an August 2026 search.

Operator

Unknown — no operator-published source (own domain, IR page, peering policy, looking glass, or NANOG/RIPE list post under the operator's own name) was found naming AS918 as of an August 2026 search [Unknown]

Country / RIR

Country Unknown — no permitted operator-published source identifies the holder's country [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS918 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no operator-published source found [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above — no confirmed public abuse or security-incident association found as of an August 2026 search, though Spamhaus's ASN-check page and AbuseIPDB's ASN page were both inaccessible (403/404) rather than checked clean

Network & routing

Network type

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

Size

1 IPv4 prefix and 1 IPv6 prefix originated; an estimated 256 IPv4 addresses (a /24), as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS918

Routing/peering

1 distinct neighboring ASN observed by RouteViews on 2026-08-20 (AS3399; peer_count=1 matches the full peers list, no cap truncation applies) — undirected AS-path adjacency, not a customer/upstream/peer classification. The CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA) carries zero rows with AS918 as either origin or counterparty, so relationship direction is unclassified among published neighbours, not a confirmed absence. Peering policy: Unknown [Confirmed for the neighbor count; Unknown for relationship roles and policy] — the RouteViews BGP routing data (CC BY 4.0) AS918, 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 usage [Unknown]

Related ASNs

AS3399 (sole neighboring ASN observed by RouteViews on 2026-08-20; undirected adjacency only, not a confirmed relationship) [Confirmed for the adjacency; Unknown for its nature] — the RouteViews BGP routing data (CC BY 4.0) AS918

Related fields

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

Analyst note

Minimal but actively routed ASN — a single /24 and a single IPv6 prefix, one observed neighbor, as of the 2026-08-20 RouteViews snapshot. No operator-published material naming AS918 was found despite an exhaustive August 2026 search; two candidate domains from third-party directories both failed TLS certificate validation and were not used. CAIDA's relationship cache (dataset date 2026-08-01) classifies zero relationships touching AS918 among published neighbours — unclassified, not zero-confirmed. 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.