AS667

AS667 (DNIC-AS-00667) is an ARIN-registered autonomous system assigned to the United States Department of Defense that is registry-active but currently dormant in global BGP routing — it announces zero IPv4 and zero IPv6 prefixes as of 2026-07-18, corroborated independently by RIPEstat, CAIDA ASRank, and Hurricane Electric's BGP Toolkit.

ARIN RDAP records the autnum's top-level registration event as 1990-04-19, with a last-changed date of 2025-09-12. The registrant is the U.S. Department of Defense (ARIN org handle USDDD), with NOC, technical, and administrative contacts registered at DISA-Columbus, Ohio — the same site associated with the DoD Network Information Center (DNIC) numbering block.

RIPEstat's routing-status data shows exactly one historical BGP sighting under this origin: 91.219.56.0/22, seen once on 2010-10-17 and never again (first_seen equals last_seen) — a stale, sixteen-year-old anomaly, not current announced space. CAIDA's customer cone for AS667 is a singleton: itself only, with zero prefixes, zero addresses, and zero observed upstream or peer relationships.

No public peering policy exists for AS667 — PeeringDB has no listing (peeringdb.com/asn/667 returns HTTP 404) — consistent with a non-commercial, DoD-administered network rather than a transit or content operator. No dedicated public website describing this specific ASN's operational purpose was located; ARIN RDAP remains the sole first-party source.

Operator

United States Department of Defense (DoD) (ARIN org handle USDDD) [Confirmed] — https://rdap.arin.net/registry/autnum/667

Country / RIR

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

Allocated

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

Org status

Active (ARIN RDAP status field); registrant U.S. Department of Defense, 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — https://rdap.arin.net/registry/autnum/667

Contacts

abuse/NOC — disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (handle MIL-HSTMST-ARIN); administrative — disa.columbus.ns.mbx.arin-registrations@mail.mil (handle REGIS10-ARIN); both at DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/667

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-18; not on Spamhaus ASN-DROP; no NANOG/seclists mentions

Network & routing

Network type

U.S. government/military network (DoD), part of the DNIC numbering block administered from DISA-Columbus, OH; not a commercial ISP/transit/content network [Likely] — https://rdap.arin.net/registry/autnum/667

Size

dormant — 0 IPv4/IPv6 prefixes, 0 addresses currently announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=667, https://api.asrank.caida.org/v2/restful/asns/667

Routing/peering

NOT announced — 0/325 IPv4 RIS peers and 0/320 IPv6 RIS peers see this origin; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB listing [Confirmed] — https://stat.ripe.net/data/as-overview/data.json?resource=667, https://www.peeringdb.com/asn/667

RPKI

not assessable — no announced prefixes, so no ROAs to validate; bgp.he.net shows 0 valid/invalid RPKI prefixes [Confirmed] — https://bgp.he.net/AS667

Notable usage

one historical BGP sighting of 91.219.56.0/22 on 2010-10-17, never repeated; otherwise no current or documented past routing use found [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=667

Analyst note

Registry-active but routing-dormant DoD/DNIC ASN. No public peering policy, no operator website beyond the ARIN registry record, and no community/incident visibility found (NANOG, Reddit searches returned nothing). Clean, quiet ASN.