AS330

AS330 is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD). It is not held as a standalone object: ARIN records it as part of a contiguous block handle, DNIC-ASBLK-00306-00371, spanning AS306 through AS371, administered by the DoD Network Information Center (DNIC) and operated day-to-day by the Defense Information Systems Agency (DISA) out of the DISA-Columbus facility in Whitehall/Columbus, Ohio. The block's top-level ARIN registration event is dated 1989-06-30, a first-party RIR fact that serves as the allocation date for the numbers in the block. The key triage point for AS330 is that it is effectively dormant: every routing source consulted (RIPEstat as-overview, RIPEstat routing-status, RIPEstat announced-prefixes, bgp.he.net, bgp.tools, Qrator Radar) agrees it announces zero IPv4 and zero IPv6 prefixes, with 0/326 IPv4 and 0/324 IPv6 RIS peers seeing it and zero observed neighbours. CAIDA AS Rank could not be consulted (the API returned HTTP 502), so rank and customer-cone figures are unknown rather than zero-confirmed. RPKI posture is not assessable because there are no active originations and therefore no ROAs to validate. No notable public abuse signal was found as of June 2026 — AS330 is absent from Spamhaus ASN-DROP, the ipapi.is most-abusive list, and CleanTalk metrics, and Qrator Radar shows zero hijacks, leaks, or bogons — consistent with a clean, reserved DoD ASN. The widely discussed 2021 DoD/AS8003 prefix-announcement episode involved a different ASN and does not implicate AS330.

Operator

United States Department of Defense (DoD); administered by the DoD Network Information Center (DNIC), operated by DISA; ARIN org handle USDDD [Confirmed] — ARIN RDAP autnum/330, ipinfo.io/AS330

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), ARIN RDAP

Allocated

1989-06-30 (ARIN registry date for the DNIC-ASBLK-00306-00371 block top-level autnum event — a first-party RIR fact, NOT an IEEE date); last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events

ASN block

DNIC-ASBLK-00306-00371 (AS306–AS371), registrant United States Department of Defense (DoD), org handle USDDD [Confirmed] — ARIN RDAP autnum/330, entity/USDDD

Org status

active U.S. federal government agency. DISA is a Combat Support Agency of the DoD, headquartered at Fort George G. Meade, MD [Confirmed for agency status; size figures Likely per Wikipedia] — Wikipedia (DISA), ARIN RDAP

Contacts

abuse/NOC/technical disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (handle MIL-HSTMST-ARIN); admin/technical disa.columbus.ns.mbx.arin-registrations@mail.mil (handle REGIS10-ARIN); +1-844-347-2457 ext2; DISA-Columbus, 300 North James Road, Whitehall, OH 43213 (registrant address 3990 E. Broad Street, Columbus, OH 43218)

[Confirmed] — ARIN RDAP autnum/330, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-28 — not in Spamhaus ASN-DROP, ipapi.is most-abusive top-1000, or CleanTalk (empty metrics); Qrator Radar shows 0 hijacks, 0 leaks, 0 bogons; no AS330-specific NANOG threads. The 2021 DoD/AS8003 announcement episode involved a different ASN

Network & routing

Network type

U.S. federal government / military network; AS330 is a reserved/legacy DoD ASN currently inactive in global BGP. DISA manages the Defense Information Systems Network (DISN), including NIPRNET, SIPRNET, and JWICS [Confirmed] — bgp.he.net/AS330, Wikipedia (DISA)

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; announced=false [Confirmed] — RIPEstat as-overview / routing-status / announced-prefixes (2026-06-28)

Routing/peering

NOT announced — 0 RIS peers seeing it (0/326 v4, 0/324 v6), 0 observed neighbours; no upstreams or peers visible in any source [Confirmed]. No public peering policy; DoD/DISN external connectivity is governed by internal DISA policy (DoDI 8010.01 / DISN Connection Process Guide), not a commercial policy

[Confirmed for absence of public policy] — RIPEstat routing-status, bgp.tools/as/330

RPKI

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

AS rank / customer cone

Unknown — CAIDA AS Rank API returned HTTP 502; rank and cone could not be retrieved [Unknown] — api.asrank.caida.org (502)

Notable usage

AS330 is one number within the legacy DoD block AS306–AS371 allocated to the Department of Defense on 1989-06-30 and administered by DNIC at the DISA-Columbus facility. Other ASNs in the same block (e.g. AS337) are active and originate DoD prefixes, but AS330 itself originates nothing publicly; much DoD routing (NIPRNET/SIPRNET) is internal and not visible to public collectors [Confirmed for AS330 inactivity; Likely for sibling-ASN activity per third-party DB] — ARIN RDAP autnum/330, bgp.tools

Analyst note

Encountered as a dormant/reserved ASN inside a contiguous DoD block (AS306–AS371) registered to the U.S. Department of Defense via DISA-Columbus. WHOIS/RDAP resolves to the DoD, but AS330 announces nothing in global BGP. The "Ritchie-Duff Networks" association tested by community research is unverified and does not appear in any source — not adopted. Clean, inactive ASN.