Autonomous system detail

AS617

Not announced

Operated by DNIC-ASBLK-00616-00665 - United States Department of Defense (DoD).

Summary

// analyst note
One member of a single ARIN autnum record spanning AS616-AS665, all registered to the DoD (org USDDD); allocated_date is the block's own RDAP top-level registration event, not a per-ASN date. Currently unannounced across RIPEstat and CAIDA.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; not in Spamhaus ASN-DROP, GreyNoise, AbuseIPDB, or NANOG archives specifically naming AS617.
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: High

AS617 is a legacy autonomous system number registered under ARIN as part of the DNIC-ASBLK-00616-00665 block, a single autnum record spanning AS616 through AS665 that ARIN assigns collectively to the United States Department of Defense (DoD, org handle USDDD). The block's top-level RDAP registration event dates to April 19, 1990, and its most recent "last changed" event is September 12, 2025. Administratively, the block is managed by the Defense Information Systems Agency out of DISA-Columbus (3990 E. Broad Street / 300 North James Road, Columbus/Whitehall, Ohio), with a dedicated abuse and NOC mailbox rather than a public-facing operator site — there is no PeeringDB network record for ASN 617, and the DoD's nic.mil hostmaster domain was unreachable during this check. Every routing source consulted (RIPEstat, CAIDA AS Rank) agrees AS617 is currently unannounced: zero IPv4 and IPv6 prefixes, zero RIS peer visibility, and a customer cone consisting only of itself. No public abuse signal was found as of July 2026, consistent with a dormant, non-commercial government allocation rather than an actively routed network.

Operator
United States Department of Defense (DoD), org handle USDDD; administered by the Defense Information Systems Agency (DISA-Columbus) [Confirmed] — https://rdap.arin.net/registry/autnum/617
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/617 ; https://stat.ripe.net/AS617
Allocated
1990-04-19 (ARIN RDAP top-level registration event for the AS616–665 block, which includes AS617); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/617
Org status
ARIN RDAP status "active" for the top-level block record containing AS617 [Confirmed] — https://rdap.arin.net/registry/autnum/617
Website
no dedicated public operator website for AS617; DoD's nic.mil hostmaster domain did not resolve during this check; parent agency site (disa.mil) publishes no ASN/peering-specific page [Likely] — https://www.disa.mil

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 across Spamhaus ASN-DROP, GreyNoise, AbuseIPDB, and NANOG archives specifically naming AS617; this is an absence finding, not a clean-bill guarantee, given the ASN's limited public routing visibility

[Likely] — https://www.spamhaus.org/blocklists/spamhaus-blocklist/ ; https://seclists.org/nanog/

Network & routing

Network type
government/military administrative network block (non-commercial); no PeeringDB network record found for ASN 617 [Likely] — https://www.peeringdb.com/api/net?asn=617
Size / routing
NOT currently announced — 0 IPv4 and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS617#tabId=routing ; https://asrank.caida.org/asns/617
Routing/peering
0 of 327 RIS peers see any v4 announcement, 0 of 322 see any v6; CAIDA asnDegree all zero (customer 0, peer 0, provider 0); no upstreams, peers, or IXP presence observed; cliqueMember/seen both false [Confirmed] — https://stat.ripe.net/AS617#tabId=routing-status ; https://asrank.caida.org/asns/617
Peering policy
none publicly published; DISA's general DISN Connection Process Guide describes DoD component connection/sponsorship procedures, not an open peering policy for this ASN [Unknown] — https://www.disa.mil/network-services/~/media/files/disa/services/disn-connect/references/disn_cpg.pdf
RPKI
not assessable — AS617 announces no prefixes, so there is no route to validate against a ROA [Unknown] — https://stat.ripe.net/AS617
CAIDA AS rank
79459; asnName "DNIC-ASBLK-00616-00665", source ARIN [Confirmed] — https://asrank.caida.org/asns/617
Geo footprint
CAIDA reports latitude/longitude 0,0, a placeholder and not a real coordinate; registrant/contact addresses place the org in Columbus/Whitehall, Ohio, US [Confirmed] — https://rdap.arin.net/registry/autnum/617
Notable usage
AS617 itself is dormant (0 announced prefixes, 0 peers per ipinfo.io, data last updated 2023-09-12); it sits within the same DoD DNIC allocation family as other DISA-managed ASNs discussed on NANOG (e.g. AS749, "DoD Network Information Center") [Likely] — https://ipinfo.io/AS617 ; https://community.nanog.org/t/squat-space-is-now-being-advertised-by-as-749-dod-network-information-center/54395
Related ASNs
part of ARIN block AS616–AS665 (DNIC-ASBLK-00616-00665); a related DoD DNIC ASN, AS665, is separately corroborated by third-party whois as the same registrant and 1990-04-19 registration date [Likely] — https://whois.ipip.net/AS665
Registered as
single ARIN autnum record handle "AS616", name "DNIC-ASBLK-00616-00665", startAutnum 616 / endAutnum 665 — AS617's allocation date is inherited from this block-level registration, not a per-ASN record [Confirmed] — https://rdap.arin.net/registry/autnum/617
Analyst note
Encountered as one member of a large DoD-administered ARIN block (AS616–665) rather than an individually-allocated ASN; the block's own registration date is used as allocated_date per RIR convention for DNIC blocks. AS617 is currently dormant/unannounced across all routing sources checked.
[ 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.