AS847

AS847 is a registered-but-dormant route-server ASN held by Richmond-IX Corporation (doing business as Ninja-IX) that announces zero IPv4 and zero IPv6 prefixes, has zero RIS-visible BGP peers, and shows no active exchange participation in current routing data as of an August 2026 check.

ARIN records the registrant as Richmond-IX Corporation (org handle RC-983, Phoenix, AZ), while PeeringDB files the AS847 network under "Ninja-IX Corporation" (org_id 7483) at the same address. A companion PeeringDB page for a sister exchange, Ninja-IX Richmond, states the IX is "owned by Richmond-IX Corporation and managed by Ninja-IX Corporation" — the likely explanation for the naming split, though that sentence names Richmond, not Santa Clara.

ARIN's autnum record gives a top-level registration event of 2022-06-16 and a last-changed event of 2023-04-24; both are Confirmed first-party RIR facts. Sibling ASN AS848 (NINJA-IX-MEMPHIS) shares the same registrant and the identical 2022-06-16 registration date, consistent with a block of route-server ASNs allocated together to Richmond-IX Corporation.

ARIN's resource name, SANTACLARA-IXP, points to a "Santa Clara-IX (Ninja-IX)" exchange, but a third-party IXP directory lists it with zero ASNs and zero locations, last updated 2022-09-16. Santa Clara does not appear in the operator's current Markets page (Auburn, Charlotte, Norfolk, Raleigh, Richmond, Dallas, Houston, Las Vegas, Phoenix, Sacramento, Hawaii, Bahamas) or its live peering-matrix portal, which lists only Phoenix, Sacramento, and Dallas.

RIPEstat and CAIDA agree AS847 originates nothing: 0 IPv4/IPv6 prefixes, a customer cone limited to the ASN itself, and 0 CAIDA-measured upstreams or peers. CAIDA AS rank is 79,459, near the bottom of the global table. With no announced prefixes there are no ROAs, so RPKI status is not assessable rather than validated.

Operator

Richmond-IX Corporation (ARIN registrant, org RC-983, Phoenix, AZ); PeeringDB network filed under Ninja-IX Corporation (org_id 7483), same address — stated as an owned/managed split on a sister exchange's PeeringDB page

[Likely] — https://whois.arin.net/rest/org/RC-983, https://www.peeringdb.com/api/org/7483, https://www.peeringdb.com/ix/1490

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/847

Allocated

2022-06-16 (ARIN RDAP autnum top-level registration event); last changed 2023-04-24 [Confirmed] — https://rdap.arin.net/registry/autnum/847

Org status

ARIN RDAP status "Active" (registry flag, not a traffic claim); registrant org RC-983 record dates to 2017-10-24 (org record date, distinct from the ASN's own allocation date) [Confirmed] — https://rdap.arin.net/registry/autnum/847, https://whois.arin.net/rest/org/RC-983

Contacts

No publishable contact: the sole ARIN POC (EMMON3-ARIN) is an individual-kind vCard, withheld per policy; no group/role mailbox exists on the record. HQ 530 E McDowell Rd, Suite PMB 107-605, Phoenix, AZ 85004 [Confirmed] — https://rdap.arin.net/registry/autnum/847

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of an August 2026 search — not in Spamhaus, AbuseIPDB (404, no listing exists), IPQualityScore, or NANOG mailing list archives

Network & routing

Network type

Internet Exchange Point route-server ASN; PeeringDB info_type = "Route Server"; ARIN resource name SANTACLARA-IXP [Confirmed] — https://www.peeringdb.com/api/net?asn=847, https://rdap.arin.net/registry/autnum/847

Size

dormant — 0 IPv4 / 0 IPv6 announced prefixes, 0 estimated addresses; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS847, https://asrank.caida.org/asns/847

Routing/peering

NOT announced — 0/327 RIS v4 peers, 0/322 RIS v6 peers see this ASN; CAIDA degree 0 customer/0 peer/0 provider; CAIDA seen=false, cliqueMember=false [Confirmed]. PeeringDB policy_general = "Open" but no operator-hosted policy_url found

[Likely] — https://stat.ripe.net/AS847, https://asrank.caida.org/asns/847, https://www.peeringdb.com/api/net?asn=847

RPKI

not assessable — zero announced prefixes, no ROAs to validate [Confirmed] — https://stat.ripe.net/AS847

Notable usage

ARIN name references a "Santa Clara-IX (Ninja-IX)" exchange, but a third-party IXP directory shows 0 ASNs/0 locations (last updated 2022-09-16) and Santa Clara is absent from the operator's current Markets list and live peering-matrix portal — appears allocated but unused as of an August 2026 check [Likely] — https://ixpdb.euro-ix.net/en/explore/ixp/1132/, https://ninja-ix.net/Markets.html, https://portal.ninja-ix.net/peering-matrix

Related ASNs

AS848 (NINJA-IX-MEMPHIS), same registrant org RC-983 and identical 2022-06-16 registration date, consistent with a block allocation [Likely] — https://whois.arin.net/rest/asn/AS848

Analyst note

registered-but-dormant IXP route-server ASN; ARIN registrant (Richmond-IX Corporation) and PeeringDB operator (Ninja-IX Corporation) share a Phoenix address consistent with an owned/managed split documented on a sibling exchange page, not one naming AS847 directly; treat notable_usage as historical/inactive rather than live [Likely]