AS670

AS670 is an actively-routed U.S. Army/DoD autonomous system, registered with ARIN under the DNIC (Defense Network Information Center) block as DNIC-AS-00670. Its registry name traces to Headquarters, USAISC (U.S. Army Information Systems Command, inactivated as a command in 1996), but the ASN itself remains live: it currently announces one IPv4 prefix, 155.85.160.0/24 (256 addresses), visible to 324 of 325 RIPE RIS route-collector peers.

ARIN's RDAP record shows a top-level autnum registration date of 1990-04-30, independently corroborated by bgp.tools. The registrant address is Fort Huachuca, AZ — home to Army network and intelligence commands — while the abuse/technical contact routes through DISA Columbus in Whitehall, OH. The autnum record was last changed 2011-08-02; the underlying org record (HEADQU-3) was more recently updated in 2025, indicating ARIN still actively maintains the registration.

BGP data agrees the network is small and quiet: CAIDA ranks it 79,459 globally, with a customer cone of just itself (0 downstream prefixes) and no observed IX presence. Third-party BGP lookers (bgp.he.net, bgp.tools) each report a single upstream/peer, AS1733 (U.S. Department of Defense), consistent with private DoD interconnection rather than commercial transit; AS670 has no PeeringDB listing and no public peering policy.

Operator / registry name

DNIC-AS-00670 — Headquarters, USAISC (U.S. Army Information Systems Command; org handle HEADQU-3) [Confirmed] — https://rdap.arin.net/registry/autnum/670, https://whois.arin.net/rest/org/HEADQU-3

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)

Allocated

1990-04-30 — ARIN RDAP autnum TOP-LEVEL "registration" event (eventDate 1990-04-30T00:00:00-04:00), corroborated independently by bgp.tools; last changed 2011-08-02 [Confirmed] — https://rdap.arin.net/registry/autnum/670

Org status

active per ARIN RDAP status field; org record HEADQU-3 last updated 2025-03-13 [Confirmed] — https://rdap.arin.net/registry/autnum/670, https://whois.arin.net/rest/org/HEADQU-3

Website

none found — no public operator site; internal DoD/Army network resource [Unknown]

Abuse contact

disa.columbus.ns.mbx.arin-registrations@mail.mil (authoritative RIR: ARIN)

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-18 across Spamhaus ASN-DROP, CleanTalk, and community bad-ASN blocklists; no confirmed BGP hijack/route-leak history found (NANOG archive search coverage incomplete) [Likely for no-abuse-signal; Unknown for hijack history] — https://www.spamhaus.org/resource-hub/dnsbl/the-return-of-the-asn-drop/, https://cleantalk.org/blacklists/asn

Network & routing

Network type

U.S. military (Army/DoD) internal network under ARIN's DNIC block; not a commercial ISP, transit, or content network [Confirmed] — https://rdap.arin.net/registry/autnum/670

Size / routing

announces 1 IPv4 prefix (155.85.160.0/24, 256 addresses); 0 IPv6 prefixes; visible to 324/325 RIS v4 peers, 0/321 v6 peers [Confirmed] — RIPEstat routing-status for AS670

CAIDA rank / cone

AS rank 79459; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; not a clique member, not "seen" in CAIDA topology [Confirmed] — CAIDA ASRank for AS670

Upstream/peer

AS1733 (United States Department of Defense), sole observed adjacency [Likely] — https://bgp.he.net/AS670, https://bgp.tools/as/670

Peering policy

none public; no PeeringDB record (peeringdb.com/asn/670 returns 404, live-checked) [Confirmed for absence] — https://www.peeringdb.com/asn/670

RPKI

Unknown — rpki-validation requires an explicit prefix and was not run for this ASN-level pass; bgp.he.net shows no documented ROA for the announced block [Unknown] — https://bgp.he.net/AS670

Geo footprint

US only; registrant address Fort Huachuca, AZ; abuse/technical POC address Whitehall, OH (DISA Columbus) [Confirmed] — https://rdap.arin.net/registry/autnum/670

ASN

AS670 [Confirmed] — https://rdap.arin.net/registry/autnum/670

Analyst note

legacy DNIC/Army registration name (Headquarters, USAISC, inactivated 1996) but the ASN itself is live-routed today, not dormant; likely operational custodian is a NETCOM TNOSC per registrant address, though no registry field states a succession verbatim [Likely]