Autonomous system detail

AS314

Not announced

Operated by DNIC-ASBLK-00306-00371 - United States Department of Defense (DoD).

Summary

// analyst note
Dormant/legacy ASN inside a DoD block object. ARIN registers AS306–AS371 as a single autnum (DNIC-ASBLK-00306-00371); the top-level registration event 1989-06-30 is the block's allocation date. No live routing: RIPEstat announced=false, 0 RIS peers, 0 neighbours (2026-06-27). CAIDA AS Rank unavailable (HTTP 502); RPKI not assessable. allocated_date taken from the autnum top-level registration event, not from entity/org decoy events (MIL-HSTMST-ARIN 1993-05-26, USDDD 2007-01-12).
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-28; not in Spamhaus ASN-DROP, no NANOG threads, no threat-feed hits.
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

AS314 is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD), administered through the DoD Network Information Center (DNIC) and operated via the Defense Information Systems Agency (DISA). It is not a standalone allocation: ARIN registers it as one slot inside the block object DNIC-ASBLK-00306-00371, a single RDAP autnum spanning AS306 through AS371 (66 ASNs) that the registry allocated to the DoD on 1989-06-30. The key triage point for AS314 is that it is dormant. Every routing source consulted agrees it announces zero IPv4 and zero IPv6 prefixes, is not present in the global routing table (announced=false per RIPEstat, queried 2026-06-27), and shows zero RIS peers and zero observed neighbours. The only routing history RIPEstat retains is a narrow window of brief BGP visibility between 2001-09-26 (199.33.16.0/24) and 2003-01-21 (130.38.0.0/16), after which the ASN went quiet. RPKI posture is not assessable because there are no active originations and therefore no ROAs to validate, and CAIDA AS Rank was unavailable (HTTP 502) so no rank or customer-cone figure could be obtained. No public abuse signal was found as of 2026-06-28 — AS314 is not in the Spamhaus ASN-DROP list (timestamped 2026-06-25), and no NANOG threads or threat-feed hits surfaced. Registry contacts route to DISA's Columbus, Ohio facility. This is a clean, inactive government/military ASN held in a reserved legacy DoD block.

Operator
United States Department of Defense (DoD), administered by the DoD Network Information Center (DNIC), operated via DISA [Confirmed] — ARIN RDAP autnum/314 (registrant USDDD), https://rdap.arin.net/registry/autnum/314
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=314
Allocated
1989-06-30 (ARIN registry date for the DNIC-ASBLK-00306-00371 block top-level autnum, which covers AS314; NOT an IEEE date — IEEE publishes no ASN registration dates); block last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events, https://rdap.arin.net/registry/autnum/314
AS name / registry name
DNIC-ASBLK-00306-00371 [Confirmed] — ARIN RDAP autnum/314 name field
Org status
active registration (block status: active per ARIN RDAP); registrant entity USDDD, United States Department of Defense, 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — ARIN RDAP autnum/314
Contacts
abuse/NOC disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; +1-844-347-2457 ext2; handle MIL-HSTMST-ARIN; DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — ARIN RDAP autnum/314, RIPEstat abuse-contact-finder
Website
https://www.disa.mil (operating agency; no AS314-specific public page exists) [Likely] — disa.mil

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-28 — not in Spamhaus ASN-DROP (timestamp 2026-06-25), no NANOG threads, no threat-feed hits; absence of public evidence does not rule out classified/non-public DoD incidents

[Likely] — spamhaus.org/drop/asndrop.json, seclists.org/nanog, bgp.he.net/AS314

Network & routing

Network type
government / military; AS314 is a legacy/dormant slot in a DoD ASN block (AS306–AS371) [Confirmed] — ARIN RDAP autnum/314, bgp.he.net/AS314, bgp.tools/as/314
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes [Confirmed] — RIPEstat routing-status (announced=false), https://stat.ripe.net/data/routing-status/data.json?resource=314
Routing/peering
NOT announced — announced=false; 0 RIS peers seeing it (0/323 v4, 0/321 v6); 0 observed neighbours; no upstreams or peers visible in any source [Confirmed] — RIPEstat as-overview / routing-status (2026-06-27)
Routing history
brief BGP visibility from 2001-09-26 (first seen, 199.33.16.0/24) to 2003-01-21 (last seen, 130.38.0.0/16); none since [Confirmed] — RIPEstat routing-status, https://stat.ripe.net/data/routing-status/data.json?resource=314
RPKI
not assessable — AS314 announces no prefixes, so there are no ROAs to validate; RPKI validation skipped (no prefix) [Unknown] — RIPEstat rpki-validation (skipped, no --prefix)
AS rank / customer cone
Unknown — CAIDA AS Rank API returned HTTP 502; not obtainable this run [Unknown] — api.asrank.caida.org (502)
Peering policy
Unknown — no PeeringDB entry for AS314 (404); DoD publishes no open peering policy for its reserved block members [Confirmed for absence] — https://www.peeringdb.com/asn/314
Notable usage
AS314 is a reserved/unactivated slot in the DoD's DNIC-ASBLK-00306-00371 block (AS306–AS371), managed by DISA's Columbus facility; currently advertising no prefixes [Confirmed] — ARIN RDAP autnum/314, bgp.he.net/AS314
Analyst note
Encountered as a dormant legacy ASN inside a DoD block object; WHOIS resolves to the U.S. DoD via DISA Columbus, but the ASN carries no live routing. Clean, inactive ASN. Community angle abstained (no public NANOG/Reddit/forum footprint) — honest null, not refutation.
[ 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.