AS580

AS580 is a legacy, low-numbered autonomous system registered under ARIN's DNIC (Defense Network Information Center) block to the United States Department of Defense. The ARIN RDAP autnum record's top-level registration event dates the allocation to 1990-02-07, with the record most recently changed 2025-09-12 (a contact-validation update, not a new allocation). Administration is handled by DISA (Defense Information Systems Agency) Columbus, whose NOC/abuse and registration-services contacts appear on the record. Routing-wise, AS580 is currently dormant: RIPEstat shows zero IPv4 and zero IPv6 prefixes announced, with 0 of 325 v4 and 0 of 322 v6 RIS peers seeing it, and CAIDA ASRank places it at rank 79,459 with a customer cone of just the ASN itself (0 prefixes, 0 addresses) and zero degree in every category (customer/peer/provider/total). It was not always inactive: RIPEstat routing history shows two /23 blocks (140.16.104.0/23 and 140.17.16.0/23) announced under AS580 between 2019-05-15 and 2022-06-15, after which announcements stopped. No PeeringDB entry exists for AS580, and no public peering policy is documented — DISA's published connection-process material describes internal DoD-component approval flows, not an open peering posture. No notable public abuse signal was found across Spamhaus DROP/SBL, several open ASN blocklist aggregators, CleanTalk/firehol feeds, or NANOG archives as of 2026-07-11; NANOG does carry unrelated squat-space controversy threads about other DoD-linked ASNs (AS8003/GRSCORP, AS749/DNIC) but none name AS580.

Operator

United States Department of Defense (DoD), registration administered by DISA Columbus NIC [Confirmed] — https://rdap.arin.net/registry/autnum/580

RIR handle

AS580 / DNIC-AS-00580 [Confirmed] — https://rdap.arin.net/registry/autnum/580

Country / RIR

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

Allocated

1990-02-07 (ARIN RDAP autnum TOP-LEVEL 'registration' event — the first-party RIR allocation date; entity-level POC/org dates of 1993-05-26, 2009-06-24, and 2007-01-12 are decoy contact-record dates and excluded); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/580

Org status

RDAP record status Active (contacts validated 2025-09-12); operationally dormant — no announced prefixes and no responding hosts observed in current scans [Likely] — https://rdap.arin.net/registry/autnum/580, https://ipinfo.io/AS580

Contacts

NOC/Abuse/Tech — MIL-HSTMST-ARIN, disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil, +1-844-347-2457 ext. 2; Admin/Tech (Registration) — REGIS10-ARIN, disa.columbus.ns.mbx.arin-registrations@mail.mil; location DISA-Columbus, 300 North James Road, Whitehall, OH 43213, US

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

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-11 — checked Spamhaus DROP/ASN-DROP/SBL, open ASN blocklist aggregators (bad-asn-list variants, ASN-BlackList, ASN_LIST), CleanTalk/firehol blocklist-ipsets, and NANOG archives; NANOG has unrelated squat-space threads about other DoD-linked ASNs (AS8003/GRSCORP, AS749/DNIC) that do not name AS580

Network & routing

Network type

U.S. federal government / military network (DoD), not a commercial ISP; currently unrouted [Likely] — https://ipinfo.io/AS580

Size

currently dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / announced-prefixes for AS580; CAIDA ASRank for AS580

Routing/peering

NOT currently announced — 0/325 v4 and 0/322 v6 RIS peers seeing it; CAIDA degree total 0 (customer 0, peer 0, provider 0); historically announced 140.16.104.0/23 → 140.17.16.0/23, 2019-05-15 to 2022-06-15 [Confirmed] — RIPEstat routing-status for AS580

Peering policy

Unknown / not publicly documented — no PeeringDB record for ASN 580 (404); DISA's DISN Connection Process Guide covers internal DoD-component approval, not a public peering policy

[Unknown] — https://www.peeringdb.com/asn/580, https://dl.dod.cyber.mil/wp-content/uploads/connect/CPG/ConnProcGuide.html

RPKI

not assessable — RIPEstat rpki-validation was skipped because it requires a prefix argument, and AS580 has no currently announced prefix to validate [Unknown] — RIPEstat rpki-validation (skipped) for AS580

Notable usage

legacy DNIC-block ASN (IANA 16-bit range 1–1876, ARIN-assigned) registered to DoD in 1990; announced two /23 blocks 2019–2022 but shows no announced space today, consistent with a held-but-currently-unrouted DoD allocation

[Confirmed/Likely] — RIPEstat routing-status for AS580; https://ipinfo.io/AS580

Related ASNs

Unknown — no specific related/sibling ASN was confirmed as directly linked to AS580 in this research pass (other DoD/DNIC ASNs such as AS749 exist but no source ties them to AS580 specifically) [Unknown]

Analyst note

A legacy, low-numbered DoD DNIC ASN, allocated 1990-02-07, that was briefly re-activated for routing 2019–2022 and has since gone dormant again; no dedicated operator website or public peering policy exists for AS580 itself.