AS902

AS902 is a small, actively routed autonomous system with no identified operator: RouteViews observed it originating 3 IPv4 prefixes (an estimated 768 addresses) and 0 IPv6 prefixes on 2026-08-20, but no permitted, operator-published source names who holds or runs it.

The IANA AS Numbers registry places AS902 in block 1-1876, marked "Assigned by ARIN," confirming ARIN as the Regional Internet Registry. Allocation date is Unknown, and no country or operator region beyond that RIR assignment is confirmed.

RouteViews' 2026-08-20 snapshot lists three neighboring ASNs for AS902 — AS174, AS3356, and AS33363 — the complete observed set, since the reported peer count equals the number of ASNs listed. This is undirected AS-path adjacency, not itself a classified relationship.

CAIDA's AS Relationships dataset (dataset date 2026-08-01) infers two of these three neighbors as providers of AS902: AS174 and AS3356 each appear in the cache as a counterparty classifying AS902 as its customer, which under CAIDA's directional convention makes AS174 and AS3356 providers of AS902. AS33363 has no row connecting it to AS902 in that dataset and remains unclassified — never a peer. These are AS-path-derived inferences carried on CAIDA's own dataset date, not disclosed peering agreements or commercial arrangements, and are dated separately from the RouteViews observation above.

Repeated searches for material in which an operator identifies itself with AS902 — a peering-policy page, a network or IR page, a looking glass, or a NANOG/RIPE list post under an operator's own name — found none. Every hit was a third-party IP-intelligence directory or aggregator republishing registry data, which does not establish operator identity on this site's sourcing standard. As of an August 2026 search, no permitted source names the holder of AS902, so operator, as_name, country, org_status, network_type, and website all remain Unknown.

Route-leak / hijack

No reports connecting AS902 to a route leak, prefix hijack, or other BGP incident were found in NANOG mailing-list archives or general web search as of an August 2026 search.

CVE / malware

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

Operator

Unknown — no permitted, operator-published source identifies the holder of AS902; repeated searches surfaced only third-party IP-intelligence directories, which do not establish operator identity [Unknown]

Country / RIR

Country Unknown — no permitted source identifies AS902's operator or country of registration [Unknown]. RIR: ARIN, per IANA AS Numbers registry block 1-1876 ("Assigned by ARIN") [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no permitted source confirms the legal or organizational status of AS902's holder [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above — no notable public abuse signal found as of a 2026-08-22 check; AS902 is absent from the current Spamhaus ASN-DROP list (439 records, ASN range 245–401701, checked live)

Network & routing

Network type

Unknown — no operator-published description of this network's purpose was found [Unknown]

Size

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

Routing/peering

3 distinct neighboring ASNs observed by RouteViews on 2026-08-20 — the complete observed set (AS174, AS3356, AS33363), not a capped sample. This is undirected AS-path adjacency, not itself a customer/upstream/peer classification. Separately, CAIDA's AS Relationships dataset (dataset date 2026-08-01) infers AS174 and AS3356 as providers of AS902 — 2 inferred among published neighbours; AS33363 is unclassified in that cache and must not be reported as a peer. These are inferences from observed AS paths, not disclosed peering agreements. Peering policy: Unknown [Confirmed for neighbor count and RouteViews adjacency; CAIDA-inferred for the two provider roles; Unknown for peering policy] — the RouteViews BGP routing data (CC BY 4.0) AS902, the cached registry snapshots/caida-as-rel.csv 174,902,customer, the cached registry snapshots/caida-as-rel.csv 3356,902,customer

RPKI

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

Notable usage

Unknown — no operator-published material describing this network's purpose or usage was found [Unknown]

Related ASNs

None identified [Unknown]

Related fields

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

Analyst note

AS902 is an ARIN-registered (IANA block 1-1876), actively routed autonomous system: RouteViews observed 3 IPv4 prefixes (an estimated 768 addresses) and 0 IPv6 prefixes on 2026-08-20, with three neighboring ASNs — AS174, AS3356, and AS33363 — the complete observed set. CAIDA's AS Relationships dataset (dataset date 2026-08-01) infers AS174 and AS3356 as providers of AS902; AS33363 is unclassified and must never be called a peer. No permitted source identifies the operator as of an August 2026 search; a candidate identity recurs across third-party directories but does not meet this site's operator-binding standard and is withheld from every field. Allocation date, country, org status, RPKI posture, and IX presence are Unknown. No notable public abuse signal found as of a 2026-08-22 check.