AS848

AS848 is an active ARIN-registered autonomous system, allocated 2022-06-16 to Richmond-IX Corporation, that currently announces zero IPv4 and zero IPv6 prefixes and has no observed BGP peers or upstreams — a fully dark, unrouted ASN rather than an abandoned or hijacked one.

PeeringDB identifies AS848 as a regional-scope Route Collector ("Ninja-IX Network 20"), which plausibly explains the zero-announcement state: a route collector aggregates BGP sessions from exchange participants rather than originating its own address space. The AS is publicly branded and operated under the Ninja-IX name, a not-for-profit U.S. internet exchange operator based in Phoenix, AZ.

ARIN's registrant of record is Richmond-IX Corporation (org handle RC-983), a legal entity distinct from Ninja-IX Corporation. Ninja-IX's own PeeringDB listing for its Richmond exchange states the exchange "is owned by Richmond-IX Corporation and managed by Ninja-IX Corporation," documenting an owner/manager split rather than a data inconsistency. The ASN's on-record name, NINJA-IX-MEMPHIS, implies a Memphis-market exchange, but Memphis does not appear in the operator's current public market list, so whether that exchange is still active is Unknown.

Because AS848 announces no prefixes, RPKI validation does not apply — there are no ROAs to check, and its CAIDA customer cone is a singleton with zero downstream ASNs, prefixes, or addresses.

Operator

ARIN registrant of record is Richmond-IX Corporation (org handle RC-983, Phoenix, AZ); the ASN is publicly branded and operated under "Ninja-IX Corporation," a not-for-profit internet exchange operator — Ninja-IX's own PeeringDB page for its Richmond exchange documents an owner (Richmond-IX Corporation) / manager (Ninja-IX Corporation) split

[Likely] — whois.arin.net/rest/asn/AS848, whois.arin.net/rest/org/RC-983, peeringdb.com/ix/1490

Country / RIR

US, ARIN [Confirmed] — rdap.arin.net/registry/autnum/848

Allocated

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

Org status

ASN status "active" per ARIN; registrant org RC-983 (Richmond-IX Corporation) created 2017-10-24, last updated 2023-04-11; PeeringDB reports RIR sync status "ok" as of 2024-06-26 [Confirmed] — rdap.arin.net/registry/autnum/848, whois.arin.net/rest/org/RC-983, peeringdb.com/net/30538

Contacts

no publishable contact — the sole ARIN point of contact (EMMON3-ARIN, "Paul Emmons") is an individual-kind vCard entry withheld per this repo's personal-contact policy; no group/role mailbox exists on the record [Confirmed] — rdap.arin.net/registry/entity/EMMON3-ARIN

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of an August 2026 search of Spamhaus's informational page and the NANOG archive (explicit zero-hit search); AbuseIPDB, Talos, and Spamhaus's ASN lookup tool returned HTTP 403 (coverage gap, not a confirmed negative); the ASN is not currently routed, which further limits abuse surface [Confirmed for the negative search result; gap noted for blocked sources] — spamhaus.org/blocklists/spamhaus-blocklist, marc.info/?l=nanog&s=AS848&f=1

Network & routing

Network type

Route Collector, regional scope, per the AS848 PeeringDB network record; consistent with bgp.he.net and bgp.tools both showing 0 originated prefixes and 0 observed peers [Likely] — peeringdb.com/net/30538, bgp.he.net/AS848, bgp.tools/as/848

Size

0 IPv4 prefixes / 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — CAIDA AS Rank data for AS848; RIPEstat routing-status for resource 848 (2026-08)

Routing/peering

NOT announced — CAIDA asnDegree provider 0, peer 0; 0/327 v4 and 0/322 v6 RIS peer visibility; not a CAIDA clique member; not seen in CAIDA topology [Confirmed]. PeeringDB lists peering policy "Open," with no contract, traffic-ratio, or multi-location requirement stated; no dedicated policy document found on the operator's own site

[Likely] — CAIDA AS Rank data for AS848; RIPEstat routing-status for resource 848; peeringdb.com/net/30538

RPKI

not assessable — AS848 announces no prefixes, so there are no ROAs to validate [Confirmed] — RIPEstat rpki-validation for resource 848

Notable usage

Unknown/not publicly disclosed. On-record AS name NINJA-IX-MEMPHIS implies a Memphis-market exchange, but the operator's current public "Markets" list does not include Memphis, so whether that exchange remains active is Unknown [Unknown] — whois.arin.net/rest/asn/AS848, ninja-ix.net

Related ASNs

AS53698, cited in connection with Ninja-IX's OIX-1 certification record; relationship to AS848 (both under the Ninja-IX operator umbrella) is plausible but not independently confirmed [Likely, single-source] — peeringdb.com/asn/53698

Analyst note

AS848 is a dark, unrouted ASN best explained by its PeeringDB classification as a regional route collector for Ninja-IX rather than as an abandoned or reclaimed registration. Treat "Richmond-IX Corporation" (ARIN registrant) and "Ninja-IX Corporation" (public operator/brand) as a documented owner/manager pair, not a data error. No MAC/OUI/IEEE claim applies — this is an IX infrastructure ASN, not a hardware vendor.