Autonomous system detail

AS569

Not announced

Operated by DNIC-AS-00569 - United States Department of Defense (DoD).

Summary

// analyst note
Dormant legacy DNIC ASN. ARIN RDAP top-level autnum events[] give allocated_date 1990-01-12 and last-changed 2025-09-12; two entity-level dates (1993-05-26, 2009-06-24) and the USDDD org's own 2007-01-12 registration date are distinct administrative events, not the ASN allocation. RIPEstat and CAIDA agree: zero announced prefixes, zero RIS peer visibility, singleton customer cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-11; not identified in NANOG archives or general threat-intel searches.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: High

AS569 is a legacy autonomous system number registered under ARIN's DNIC (DoD Network Information Center) block to the United States Department of Defense, with technical, administrative, and abuse contacts routed through DISA Columbus. The ARIN RDAP autnum object's own top-level registration event dates the ASN's allocation to 1990-01-12, with a last-changed timestamp of 2025-09-12; two nearby entity-level dates in the same record (an individual contact registered 1993-05-26 and an administrative-contact group registered 2009-06-24) describe unrelated contact-object history and were deliberately not used as the allocation date. The organization record behind the ASN, USDDD, itself shows a distinct registration date of 2007-01-12, reflecting when that org handle was created or restructured in ARIN's Whois system — a separate administrative event from the ASN's own 1990-01-12 allocation. Operationally, AS569 is currently dormant: RIPEstat's as-overview flags it as not announced, and every routing metric checked (announced-prefixes, routing-status, CAIDA ASRank) shows zero IPv4/IPv6 prefixes, zero RIS peer visibility out of 327 (v4) and 322 (v6) peers, and a customer cone limited to the ASN itself. No PeeringDB record and no public abuse or NANOG-archive signal were found for this ASN as of 2026-07-11.

Operator
United States Department of Defense (DoD) — org handle USDDD, address 3990 E. Broad Street, Columbus, OH 43218, US [Confirmed] — https://rdap.arin.net/registry/autnum/569
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/569, https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=569 (authoritative_rir: arin)
Allocated
1990-01-12 (ARIN RDAP autnum top-level registration event); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/569 (top-level events[]; two entity-level dates — 1993-05-26 for contact MIL-HSTMST-ARIN, 2009-06-24 for contact REGIS10-ARIN — are decoys describing contact-record history, not ASN allocation)
Org status
active per ARIN RDAP (autnum status: active) [Confirmed] — https://rdap.arin.net/registry/autnum/569
Website
Unknown — no ASN-specific or dedicated operator page found; DISA (disa.mil) administers DoD networks generally but no page references AS569 specifically [Likely] — https://www.disa.mil/

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-11 across Spamhaus/AbuseIPDB/GreyNoise-style sources or NANOG mailing-list archives; consistent with an unannounced ASN generating no scanning/spam telemetry [Confirmed] — abuse contact disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil per https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=569

Network & routing

Network type
U.S. federal government / military network (DoD Information Network / DISN), registered under the legacy DNIC numbering block administered via ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/569
Size / routing
dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=569, https://api.asrank.caida.org/v2/restful/asns/569
Routing/peering
NOT announced — 0/327 RIS peers seeing it in v4, 0/322 in v6; CAIDA asnDegree total 0 (customer 0, peer 0, provider 0); no PeeringDB net record exists (API returned no match) [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=569, https://api.asrank.caida.org/v2/restful/asns/569, https://www.peeringdb.com/api/net?asn=569
Peering policy
not publicly published; DoD network interconnection is governed internally via the DISN Connection Process Guide rather than a public commercial-style peering policy [Likely] — https://www.disa.mil/network-services/~/media/files/disa/services/disn-connect/references/disn_cpg.pdf
RPKI
not assessable — AS569 announces no prefixes, so no ROAs exist to validate; the RPKI-validation tool itself skipped the check for lack of a supplied prefix [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json?resource=569
AS rank
CAIDA ASRank #79459 (asnName DNIC-AS-00569, source ARIN) [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/569
Notable usage
no distinct operational usage found beyond a dormant DoD registry holding; note (adjacent, NOT this ASN) that AS8003 — a separate ASN — began announcing large dormant DoD IPv4 blocks in Jan 2021, which is unrelated to AS569 and should not be merged into this record
[Confirmed] — https://www.kentik.com/blog/the-mystery-of-as8003/
ASN / handle
AS569, name DNIC-AS-00569 [Confirmed] — https://rdap.arin.net/registry/autnum/569
Org record note
the USDDD registrant org itself shows a separate "registration" date of 2007-01-12 (last changed 2025-03-13) in ARIN Whois — this is the org handle's own creation/restructure event, distinct from and not to be conflated with AS569's 1990-01-12 allocation date
[Confirmed] — https://whois.arin.net/rest/org/USDDD
Analyst note
dormant legacy DNIC military ASN; WHOIS/RDAP resolves cleanly to DoD/DISA Columbus, but the ASN carries zero live routing footprint in any source checked.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.