AS575

AS575 is a legacy ASN registered under ARIN to Headquarters, USAISC — the U.S. Army Information Systems Command — as part of the old Defense Data Network Information Center (DNIC) ASN block. The registration entry itself dates to 1990-04-01, per the ARIN RDAP autnum object's top-level registration event, making this one of the earliest ASN allocations still on record; the record was last modified in 2011-08-02. USAISC as an organization was reportedly inactivated in 1996, with its functions folded into what became U.S. Army Network Enterprise Technology Command (NETCOM), yet the ASN registration remains administratively active under DISA-Columbus custodianship (abuse/admin contact disa.columbus.ns.mbx.arin-registrations@mail.mil). Operationally the ASN is nearly dormant: RIPEstat and CAIDA both show zero IPv4 prefixes announced today, though the org historically originated 143.84.228.0/24 (first seen 2004) and still holds unannounced legacy netblocks (132.134.0.0/15, 132.136.0.0/13). The only current announcement is a single IPv6 block, 2608:16b:6100::/40, visible to 322 of 322 RIS peers since late June 2026. CAIDA's topology view places it at AS rank 79,459 with a customer cone of just itself and zero measured peer/customer/provider degree — consistent with a closed, non-transit military network rather than a commercial operator.

Operator

Headquarters, USAISC (U.S. Army Information Systems Command); registrant address Fort Huachuca, AZ [Confirmed] — https://rdap.arin.net/registry/autnum/575

Country / RIR

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

Allocated

1990-04-01 (ARIN RDAP autnum top-level registration event — first-party RIR fact); last changed 2011-08-02 [Confirmed, corroborated by two angles] — https://rdap.arin.net/registry/autnum/575 (top-level events[]), https://bgpview.io/asn/575

Org status

ARIN RDAP record status "active" (registry-record status only, not confirmed operational routing beyond the announced IPv6 block); registrant org Headquarters, USAISC [Confirmed] — https://rdap.arin.net/registry/autnum/575

Security/abuse context (NEUTRAL, DATED)

no notable public abuse or threat signal found as of 2026-07-11 across Spamhaus resources, general abuse aggregators, and NANOG-indexed search; consistent with dormant DoD infrastructure rather than a hosting/eyeball network

Network & routing

Network type

U.S. military/DoD network (non-commercial); legacy Defense Data Network (DNIC) ASN, administrative custodian DISA-Columbus, Whitehall OH [Likely] — https://rdap.arin.net/registry/autnum/575

Size

dormant for IPv4 — 0 prefixes / 0 addresses currently announced; 1 IPv6 prefix (2608:16b:6100::/40, 256 x /48s) announced since 2026-06-27; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA ASRank for AS575

Routing/peering

0 IPv4 announcements today (historically originated 143.84.228.0/24, first seen 2004; legacy netblocks 132.134.0.0/15 and 132.136.0.0/13 held but not currently routed); IPv6 /40 visible to 322/322 RIS peers; CAIDA asnDegree total/customer/peer/provider all 0

[Confirmed] — RIPEstat routing-status, https://bgpview.io/asn/575, CAIDA ASRank API

RPKI

Unknown/not evaluated — RIPEstat rpki-validation was skipped in this pass because it requires an explicit prefix parameter; no ROA/validation data obtained [Unknown] — RIPEstat rpki-validation response for AS575

Notable usage

Legacy 1990 DoD/DNIC ASN allocation; USAISC as an organization was reportedly inactivated in 1996 with functions transferred toward today's U.S. Army Network Enterprise Technology Command (NETCOM) lineage, but the ASN registration itself remains listed active under DISA-Columbus

[Likely] — https://en.wikipedia.org/wiki/Army_Network_Enterprise_Technology_Command, https://rdap.arin.net/registry/autnum/575

Peering policy / PeeringDB

Unknown — not publicly published; no PeeringDB net record exists for AS575 (API query returned HTTP 404), consistent with a closed military network [Confirmed] — https://www.peeringdb.com/api/net?asn=575

Community corroboration

no NANOG archive threads, Reddit operator discussion, PeeringDB activity, or BGP hijack/incident reports found referencing AS575 [Confirmed, negative-search finding] — searched archive.nanog.org and general web/community sources

Analyst note

A genuinely dormant legacy DoD ASN — registry-first-party dates (1990-04-01 allocation, 2011-08-02 last-changed) are well corroborated across ARIN RDAP and third-party BGP databases, but operational signals (peers, RPKI, website, related-ASN block) are largely and honestly Unknown given the closed nature of this network.