AS660

AS660 is a reserved-but-unannounced autonomous system number belonging to the U.S. Department of Defense's DNIC-ASBLK-00616-00665 block (covering AS616–AS665), registered to the DoD via ARIN. It carries zero live BGP routing today: no announced IPv4 or IPv6 prefixes, no observed peers, and no upstreams, corroborated across RIPEstat RIS, CAIDA, and bgp.he.net. This is a registry allocation, not active operating infrastructure.

The ARIN RDAP autnum record for the block shows a top-level registration event dated 1990-04-19, with the record itself last changed 2025-09-12. AS660 has no individually named registrant; it inherits the DNIC block's DoD registrant record, administered out of DISA-Columbus in Whitehall, Ohio, with abuse/NOC contact routed to a DoD hostmaster mailbox.

CAIDA's AS Rank places AS660 at 79,459 — near the bottom of the global ranking — with a customer cone limited to itself (1 ASN, 0 prefixes, 0 addresses) and an AS-degree of 0 in every direction (customer, peer, provider). RIPEstat's routing-status query shows 0 of 325 IPv4 RIS peers and 0 of 320 IPv6 RIS peers observing the ASN, matching bgp.he.net's live 0-prefix/0-peer readout.

The DoD's PeeringDB organization (org 17705) lists 21 other DoD ASNs but not AS660, and no dedicated operator page, peering policy, or AS660-specific notable-usage record was found anywhere public. That absence is consistent with AS660 being inactive/reserved space inside a larger military block rather than a standalone operating network with its own public presence.

Operator

United States Department of Defense (DoD), via DNIC-ASBLK-00616-00665 (block AS616–AS665) [Confirmed] — https://rdap.arin.net/registry/autnum/660

Country / RIR

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

Allocated

1990-04-19 (ARIN RDAP autnum top-level registration event on the DNIC block record); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/660

Org status

active (per ARIN RDAP status field on the DNIC block record) — reflects registry status, not confirmation that AS660 itself is actively announced in BGP [Confirmed] — https://rdap.arin.net/registry/autnum/660

Contacts

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (NOC/technical/abuse); registrant address 3990 E. Broad Street, Columbus, OH 43218, US [Confirmed] — https://rdap.arin.net/registry/autnum/660

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 — not in Spamhaus ASN-DROP, AbuseIPDB/IPQualityScore reference material; unrelated to the 2021 AS8003 dark-DoD-space event

Network & routing

Network type

government/military allocation block; reserved/unannounced within the DoD's DNIC range, not a named standalone operator [Confirmed for routing-visibility status; Unknown for intended operational purpose] — https://bgp.he.net/AS660

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank, bgp.he.net (2026-07-18)

Routing/peering

NOT announced — 0 of 325 v4 RIS peers and 0 of 320 v6 RIS peers see it; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed] — https://bgp.he.net/AS660

RPKI

not assessable — no announced prefixes, so there are no ROAs to validate [Confirmed] — RIPEstat rpki-validation (skipped, requires a prefix)

Notable usage

Unknown — no evidence found of active routing or public-facing service tied specifically to AS660 distinct from the broader DoD DNIC block [Unknown]

Related ASNs

part of the DNIC-ASBLK-00616-00665 range (AS616–AS665); DoD PeeringDB org 17705 lists 21 other DoD ASNs (AS3529, AS616, AS5189, AS360, AS27081, AS126, AS650, AS325, AS749, AS303, AS725, AS654, AS147, AS769, AS3541, AS244, AS95, AS138, AS39, AS124) but not AS660

[Confirmed] — https://www.peeringdb.com/org/17705

Analyst note

Encountered as a dormant DoD DNIC-block ASN with no individual operator presence; the block's top-level RIR registration date (1990-04-19) is recorded as allocated_date per RIR-first-party-fact policy, distinct from any entity-nested decoy dates in the RDAP record.