Autonomous system detail

AS615

Not announced

Operated by DNIC-AS-00615 - Headquarters, USAISC.

Summary

// analyst note
Encountered as a DoD/Army-registered ASN with an ARIN top-level allocation date recorded per registry-fact policy (1990-04-05). Notably, unlike many low-numbered dormant government ASNs, AS615 actively routed 155.85.163.0/24 for over a decade (2014-2026) before recently going dark; treat as recently-withdrawn rather than never-used. A candidate operator-website citation (usainscom.army.mil, INSCOM) conflicts with the RIR's USAISC abbreviation (Information Systems Command) and was not adopted.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17 in Spamhaus ASN-DROP/DROP, NANOG archive search, or checked community ASN blocklist repos; a bounded, non-authenticated search, not an exhaustive one.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS615 is an early, government-allocated Autonomous System Number registered under ARIN as "DNIC-AS-00615," held by the registrant handle "Headquarters, USAISC." Unlike most of the low-numbered legacy Department of Defense ASNs that have sat completely dark for decades, AS615 was actively announced in the global routing table for over a decade: RIPEstat's routing-status history shows it originating a single IPv4 block, 155.85.163.0/24, continuously from June 2014 through March 2026, before dropping off the table entirely by the time of this research pass in July 2026. Today it shows zero announced IPv4 and IPv6 prefixes, zero visible BGP peers or upstreams in CAIDA's or RIPE RIS's current topology, and a singleton customer cone (itself, 0 prefixes, 0 addresses) — consistent with a recently withdrawn, rather than never-used, government network. Administrative and abuse contact routes to DISA-Columbus, the Defense Information Systems Agency's registration desk in Whitehall, Ohio, while the underlying registrant address traces to Fort Huachuca, Arizona. One research pass surfaced a plausible-looking operator domain (usainscom.army.mil, belonging to U.S. Army INSCOM — Intelligence and Security Command) that does not match the ARIN record's "USAISC" abbreviation (commonly expanded as Army Information Systems Command); that identification is flagged as unconfirmed rather than adopted. No public abuse signal was found against AS615 in the sources checked.

Operator / registrant
DNIC-AS-00615 - Headquarters, USAISC (ARIN handle HEADQU-3; registrant address Fort Huachuca, AZ 85613) [Confirmed] — https://rdap.arin.net/registry/autnum/615
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1990-04-05 (ARIN autnum TOP-LEVEL registration event; NOT an IEEE/OUI-style date); top-level last-changed 2011-08-02 [Confirmed, agreed independently by two research angles] — https://rdap.arin.net/registry/autnum/615
Org status
ARIN registration status Active [Confirmed]. Third-party aggregator ipinfo.io separately labels it network-type "inactive" as of its own last-updated snapshot (2011-08-02) — a routing-visibility label, not an ARIN registration fact, and now superseded by the 2014-2026 announcement history above
[Likely] — https://rdap.arin.net/registry/autnum/615, https://ipinfo.io/AS615

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 in Spamhaus's ASN-DROP/DROP resource pages, NANOG mailing-list archive search, or the community ASN blocklist repos checked (bad-asn-list variants, firehol blocklist-ipsets); this is a bounded, non-authenticated search, not an exhaustive query against those services' own lookup tools

[Likely] — https://www.spamhaus.org/blocklists/do-not-route-or-peer/, https://ipinfo.io/AS615

Network & routing

Network type / operator identity
U.S. federal government / Dept. of the Army network (non-commercial). "USAISC" is commonly expanded in public histories as U.S. Army Information Systems Command, later folded into Army Signal Command/NETCOM structures. A separate research angle instead cited usainscom.army.mil (U.S. Army INSCOM — Intelligence and Security Command, a different organization with a similarly-spelled domain); that identification conflicts with the RIR's "USAISC" abbreviation and is NOT adopted here [Likely, per NETCOM history sources] — https://en.wikipedia.org/wiki/Army_Network_Enterprise_Technology_Command, https://www.globalsecurity.org/military/agency/army/netcom-history.htm
Routing history
announced a single IPv4 block, 155.85.163.0/24, continuously from 2014-06-06 to 2026-03-20 (RIPEstat routing-status first_seen/last_seen); zero prefixes announced as of this research pass (2026-07-17)
[Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=615, https://bgp.he.net/AS615
Routing/peering (current)
not seen by any of 327 RIS v4 peers or 322 RIS v6 peers; CAIDA degree total 0 (customer 0, peer 0, provider 0); no current upstreams [Confirmed]. Historically visible with one IPv4 peer, AS1733 (US DoD), per bgp.he.net's last-recorded topology
[Likely] — https://stat.ripe.net, https://api.asrank.caida.org/v2/restful/asns/615, https://bgp.he.net/AS615
RPKI
not assessable — no prefix is currently announced to validate against a ROA; RIPEstat's rpki-validation endpoint requires a prefix and was skipped [Confirmed] — https://stat.ripe.net
CAIDA AS rank
79,459 [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/615
Related ASNs
none confirmed in this pass; the one historical peer identified, AS1733 (US DoD), is not established as operator-affiliated [Unknown]
Admin/abuse/tech contact
DISA-Columbus (Defense Information Systems Agency), handle REGIS10-ARIN, 300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil [Confirmed] — https://rdap.arin.net/registry/autnum/615
Current size
0 IPv4 prefixes / 0 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/615, RIPEstat routing-status
Community/NANOG signal
none found; USAISC's reported 1996 inactivation may explain the absence of recent community discussion [Unknown] — https://en.wikipedia.org/wiki/Army_Network_Enterprise_Technology_Command
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.