AS664
Operated by United States Department of Defense (DoD), US.
Summary
- // analyst note
- Currently routed DoD block ASN. Allocated_date is the RDAP autnum top-level registration event (1990-04-19) for the containing block DNIC-ASBLK-00616-00665, deliberately distinguished from entity-level decoy dates (MIL-HSTMST-ARIN 1993-05-26, USDDD org 2007-01-12, REGIS10-ARIN 2009-06-24) on the same record. CAIDA AS rank, customer cone, and the identity of the single observed BGP neighbor were not present in supplied data and were not recoverable in this pass — reported as null rather than invented.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; not in Spamhaus ASN-DROP; 0.00% spam rate / 0 flagged IPs in CleanTalk's monthly snapshot; no NANOG/Reddit discussion found.
About this ASN.
AS664 is an actively routed autonomous system allocated to the United States Department of Defense (DoD), administered via the Defense Information Systems Agency (DISA) DoD Network Information Center in Columbus, Ohio, and it is announcing live prefixes today rather than sitting dormant.
The ASN sits inside DNIC-ASBLK-00616-00665 (AS616–AS665), a DoD-reserved block ARIN's RDAP record shows with a top-level registration date of 1990-04-19 and a last-changed date of 2025-09-12. Registrant is the U.S. Department of Defense (handle USDDD), 3990 E. Broad Street, Columbus, OH.
Currently announced routes are 199.211.166.0/23 and 199.211.168.0/23 (two IPv4 prefixes, 1,024 addresses) plus 2608:167:15::/48 (one IPv6 /48), visible to nearly all RIPE RIS peers (324/325 IPv4, 320/320 IPv6). Origination for this ASN was first observed 2009-09-23 and is still current as of 2026-07-18.
RIPEstat reports only one observed BGP neighbor and no PeeringDB net record exists for AS664, consistent with a closed, single-upstream government network rather than one running a public peering policy; the neighbor's identity was not resolvable in this pass. Some third-party aggregators (bgp.he.net, cidr-report.org) label the ASN "PENS-NET-AS" under the Navy Network Information Center, but ARIN's own record carries no Navy-specific name — that label is unverified and should not be presented as fact.
- Public abuse signal
- None found as of 2026-07-17 — AS664 is absent from Spamhaus ASN-DROP and shows a 0.00% spam rate / 0 flagged IPs in CleanTalk's monthly AS snapshot; treat as an absence-of-signal finding, not a certification.
- Community discussion
- No AS664-specific NANOG or Reddit operator threads found; the low visibility is consistent with a DoD network's operational-security posture rather than an indicator of anything unusual.
- RPKI posture
- Unknown — RIPEstat's rpki-validation lookup requires a specific prefix argument and was not evaluated in this pass, so ROA coverage for the announced prefixes is unconfirmed.
- Network exposure
- Small, stable announced footprint (2 IPv4 + 1 IPv6 prefix) behind a single observed BGP neighbor limits the attack surface visible from public routing data alone.
- Operator
- United States Department of Defense (DoD), administered via DISA / DoD Network Information Center (DoD NIC), DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/664
- Country / RIR
- US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/664
- Allocated
- 1990-04-19 (ARIN RDAP top-level registration event for containing block DNIC-ASBLK-00616-00665); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/664
- Org status
- Active [Confirmed] — https://rdap.arin.net/registry/autnum/664
- Website
- Unknown — no live dedicated official site for this ASN/block; historical nic.mil is defunct/archived-only; DISA's general site has no ASN-specific page [Confirmed absence] — https://www.disa.mil/network-services/
- Contacts
- NOC/abuse — disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil, +1-844-347-2457 ext2 (DISA-Columbus, 300 North James Road, Whitehall, OH 43213); administrative — disa.columbus.ns.mbx.arin-registrations@mail.mil [Confirmed] — https://rdap.arin.net/registry/autnum/664
Security/abuse context (neutral, dated)
no notable public abuse signal as of 2026-07-17 — not in Spamhaus ASN-DROP, 0.00% spam / 0 flagged IPs in CleanTalk's monthly snapshot, no NANOG/Reddit discussion found
Network & routing
- Network type
- government/military; classified as a stub AS with a single upstream [Confirmed] — https://ipinfo.io/AS664
- Size
- currently routed — 2 IPv4 prefixes / 1,024 addresses (199.211.166.0/23, 199.211.168.0/23) and 1 IPv6 /48 (2608:167:15::/48); first seen under this origin 2009-09-23, still announced 2026-07-18 [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=664
- Routing/peering
- 1 observed BGP neighbor (identity unresolved), no PeeringDB net record; RIS visibility 324/325 v4 peers, 320/320 v6 peers [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=664, https://www.peeringdb.com/api/net?asn=664
- RPKI
- Unknown — RIPEstat rpki-validation requires a specific prefix and was not queried in this pass [Unknown]
- Notable usage
- small DoD-administered footprint; third-party label "PENS-NET-AS" (Navy Network Information Center) appears on bgp.he.net/cidr-report.org but is NOT confirmed by ARIN or any primary DoD/Navy source [Likely, third-party only] — https://bgp.he.net/AS664, https://www.cidr-report.org/as6447/autnums.html
- Analyst note
- Actively routed DoD block ASN inside DNIC-ASBLK-00616-00665; allocated_date correctly sourced from the RDAP autnum top-level registration event (1990-04-19), not the entity-level decoy dates (1993, 2007, 2009) belonging to individual contact/registration objects on the same record.
What this network routes.
- 199.211.166.0/23
- 199.211.168.0/23
- 2608:167:15::/48
Who it talks to.
Neighbours observed by RouteViews at 2026-09-20, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.
| ASN | Operator | Role |
|---|---|---|
| AS27064 | — | upstream |