AS632

AS632 is a legacy autonomous system number held within the ARIN DNIC-ASBLK-00616-00665 block — a single registration spanning AS616 through AS665 — registered to the United States Department of Defense (DoD) and administratively managed by the Defense Information Systems Agency (DISA) out of its DISA-Columbus facility in Whitehall, Ohio (formerly the DoD Network Information Center). ARIN RDAP's top-level registration event for this block dates to April 19, 1990, with the record last changed September 12, 2025 — an administrative update, not a new allocation. Like most of the DNIC block, AS632 is presently dormant: RIPEstat, CAIDA AS Rank, and independent checks of bgp.he.net and bgp.tools all agree it announces zero IPv4 and zero IPv6 prefixes, has zero visible peers or upstreams, and sits near the bottom of CAIDA's global ranking (rank 79,459) with a customer cone containing only itself. No PeeringDB entry exists for AS632, and DISA does not publish an open peering policy — connections into the Defense Information Systems Network (DISN) instead follow a sponsored, mission-partner accreditation process. RPKI posture cannot be assessed since there are no announced prefixes to validate. No notable public abuse signal was found, though this null result is expected for an unrouted legacy allocation regardless of underlying risk, and should not be read as a clean bill of health.

Operator

United States Department of Defense (DoD); administered by DISA-Columbus, Whitehall, OH (formerly DoD Network Information Center) [Confirmed] — https://rdap.arin.net/registry/autnum/632

Country / RIR

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

Allocated

1990-04-19 (ARIN autnum TOP-LEVEL registration event for the DNIC-ASBLK-00616-00665 block, handle AS616, covering AS616–AS665 including AS632); last changed 2025-09-12 [Confirmed, cross-checked by two independent angles and independently reconfirmed via bgp.tools] — https://rdap.arin.net/registry/autnum/632, https://bgp.tools/as/632

Org status

active; DoD organization record (handle USDDD), contacts at DISA-Columbus (hostmaster-dod-nic@mail.mil, arin-registrations@mail.mil) [Confirmed] — https://rdap.arin.net/registry/autnum/632

Contacts

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (NOC/abuse); disa.columbus.ns.mbx.arin-registrations@mail.mil (registrations); DISA-Columbus, 300 North James Road, Whitehall, OH 43213; registrant org address 3990 E. Broad Street, Columbus, OH 43218 — administrative/contact addresses, not a network-derived geolocation (CAIDA lists no lat/long)

[Confirmed] — https://rdap.arin.net/registry/autnum/632, https://stat.ripe.net/AS632

IANA reference

none located; left blank rather than fabricated [Unknown]

Security/abuse context (NEUTRAL, sourced null)

no notable public abuse signal found as of 2026-07-17 (no DDoS/botnet/spam/hijack reports); this null is expected for an unrouted, zero-prefix legacy allocation and should not be read as a verified-safe rating

Network & routing

Network type

U.S. federal government / military network; part of the DoD Information Network (DODIN) / Defense Information Systems Network (DISN), operated by DISA [Likely] — https://en.wikipedia.org/wiki/Defense_Information_Systems_Agency, https://rdap.arin.net/registry/autnum/632

Size

dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS632, https://asrank.caida.org/asns/632, https://bgp.he.net/AS632, https://bgp.tools/as/632

Routing/peering

NOT announced — 0/326 v4 RIS peers and 0/322 v6 RIS peers seeing it; no upstreams or peers observed in any source; no PeeringDB entry (peeringdb.com/asn/632 returns 404, checked live) [Confirmed]. DISA governs DISN connections through a sponsored mission-partner accreditation process (DISN Connection Process Guide), not an open commercial-style peering policy [Likely] — https://stat.ripe.net/AS632, https://bgp.he.net/AS632, https://www.peeringdb.com/asn/632, https://www.disa.mil/network-services/~/media/files/disa/services/disn-connect/references/disn_cpg.pdf

RPKI

not assessable — no announced prefixes, so no ROAs exist to validate; bgp.he.net independently shows 0 RPKI-valid and 0 RPKI-invalid origins [Confirmed] — https://stat.ripe.net/AS632, https://bgp.he.net/AS632

Notable usage

part of DODIN, DISA's global DoD enterprise IT/communications infrastructure supporting DoD leadership, combatant commands, and mission partners; shares the DNIC block with 49 other DoD ASNs, and no AS632-specific sub-network or base is separately documented

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

Related ASNs

shares the single DNIC-ASBLK-00616-00665 registration with AS616 through AS665 (50 consecutive DoD-assigned autonomous system numbers) [Confirmed] — https://rdap.arin.net/registry/autnum/632

Analyst note

dormant, unrouted legacy DoD ASN inside a 50-ASN shared DNIC block. The RIR top-level registration date (1990-04-19) is recorded as allocated_date per the RIR-dates-are-first-party-facts rule — not nulled as "non-IEEE" or "database artifact" — since this is an ARIN RDAP autnum registration event, not an OUI/IEEE scrape.