AS849

AS849 is a currently dark autonomous system number — registered to Richmond-IX Corporation and operated, per PeeringDB, under the not-for-profit Ninja-IX Corporation brand — that announces zero IPv4 and zero IPv6 prefixes as of an August 2026 check. ARIN RDAP names it MIAMI-GARDENS-IXP and records a top-level registration date of 2022-06-16, independently corroborated by bgp.tools.

Every routing source checked agrees on that dark status: RIPEstat shows 0/327 RIS peers observing it on IPv4 and 0/322 on IPv6, CAIDA AS Rank places it at rank 79,459 with seen=false and a customer cone containing only itself (0 prefixes, 0 addresses), and both bgp.he.net and bgp.tools confirm it is absent from the global routing table. RPKI validation could not run because no prefixes are announced.

The RDAP registrant of record is Richmond-IX Corporation (Phoenix, AZ), while PeeringDB attributes the associated network object — a Route Server, per its info_type field — to Ninja-IX Corporation, a not-for-profit peering-exchange operator active in roughly ten US markets. Third-party directories (Euro-IX ixpdb) describe Richmond-IX and Ninja-IX as one operating entity, but no first-party statement on ninja-ix.net itself confirms that linkage for this specific ASN.

AS849's own PeeringDB network object carries no recorded facility, IX presence, or traffic figures, and no BGP-visible peers — a status consistent with an unused or standby route-server ASN. This sits alongside an active Richmond, VA exchange (QTS Richmond/RIC1) where other participants do peer; that broader exchange activity should not be read as activity on AS849 itself, since no source ties visible BGP peering specifically to this ASN.

Operator

Richmond-IX Corporation (RDAP registrant, ARIN OrgId RC-983, Phoenix, AZ) — associated network object operated under the Ninja-IX Corporation brand (PeeringDB org_id 7483, ninja-ix.net) [Confirmed for RDAP registrant; Likely for the Richmond-IX/Ninja-IX operating relationship, per third-party Euro-IX ixpdb listing, no first-party statement found] — https://rdap.arin.net/registry/autnum/849, https://www.peeringdb.com/api/net?asn=849, https://ixpdb.euro-ix.net/en/explore/organization/71886/

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/849 (abuse-contact-finder authoritative_rir=arin)

Allocated

2022-06-16 (ARIN RDAP autnum top-level registration event); last changed 2023-04-24 [Confirmed] — https://rdap.arin.net/registry/autnum/849 (independently corroborated by https://bgp.tools/as/849)

Org status

ARIN RDAP autnum status = active; PeeringDB net status = "ok" (last updated 2024-05-09); registrant contact record last-changed 2026-07-17, indicating ongoing registry activity [Confirmed] — https://rdap.arin.net/registry/autnum/849, https://www.peeringdb.com/api/net?asn=849

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. Registrant address 530 E McDowell Road, Suite 107-605, Phoenix, AZ 85004, United States [Confirmed] — https://rdap.arin.net/registry/autnum/849

Security/abuse context (NEUTRAL, DATED)

not present in Spamhaus ASN-DROP as of a 2026-07-27 snapshot; no NANOG archive thread references AS849 or Richmond-IX; no other public abuse signal found as of an August 2026 search [Likely — absence of evidence, not a comprehensive proprietary threat-intel sweep] — https://www.spamhaus.org/drop/asndrop.txt, https://seclists.org/nanog/

Network & routing

Network type

Internet Exchange Point route-server ASN — PeeringDB info_type = "Route Server" for the AS849 network object ("Ninja-IX Network 18"); part of a not-for-profit peering fabric [Confirmed] — https://www.peeringdb.com/api/net?asn=849, http://ninja-ix.net

Size

dark/dormant — 0 IPv4 prefixes / 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank, bgp.he.net, bgp.tools (2026-08)

Routing/peering

NOT announced — 0/327 RIS peers see it on v4, 0/322 on v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); CAIDA seen=false, cliqueMember=false; no upstreams or peers visible in any source [Confirmed]. PeeringDB lists an Open peering policy on the network object itself, though no externally visible BGP activity corroborates it [Confirmed for policy field; Likely that it reflects live activity] — https://stat.ripe.net/data/routing-status/data.json?resource=849, https://api.asrank.caida.org, https://www.peeringdb.com/api/net?asn=849

RPKI

not evaluable — RIPEstat skipped validation because AS849 announces 0 prefixes, so there are no ROAs to check [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json?resource=849

Notable usage

no facility, IX presence, or traffic figures recorded in PeeringDB for the AS849 network object specifically; it functions as a route-server ASN within Ninja-IX Corporation's broader not-for-profit peering fabric (~10 US markets including Richmond, VA at QTS Richmond/RIC1), alongside separate market ASNs and Ninja-IX's own primary ASN

[Likely] — https://www.peeringdb.com/api/net?asn=849, http://ninja-ix.net, https://www.peeringdb.com/ix/1490

Related ASNs

within the Ninja-IX/Richmond-IX peering fabric per PeeringDB market network objects (relationship stated by third-party directories, not confirmed first-party for AS849 specifically)

[Likely] — https://www.peeringdb.com/net/26045, https://www.peeringdb.com/net/11512, https://www.peeringdb.com/net/27497

Analyst note

sourced summary, no ownership assertion beyond confirmed facts. AS849 (MIAMI-GARDENS-IXP) is a currently dark route-server ASN registered to Richmond-IX Corporation and associated in PeeringDB with the Ninja-IX Corporation not-for-profit peering fabric. Despite the associated Richmond, VA exchange having active third-party participants, AS849 itself shows zero BGP announcements and zero visible peers across RIPEstat, CAIDA, bgp.he.net, and bgp.tools as of August 2026; that discrepancy is disclosed, not resolved. [Likely]