AS139

AS139 is one of the oldest Autonomous System Numbers still on the books, registered to the Navy Network Information Center (NNIC), a United States Department of Defense entity that manages IP address space and ASNs for U.S. Navy network infrastructure. The handle is DNIC-AS-00139, the "DNIC" prefix reflecting its origin in the Defense Network Information Center's allocations. ARIN's RDAP record dates the registration to November 25, 1987, with the autnum record last changed July 5, 2011 — these are ARIN registry events, not vendor-published dates. Day-to-day registry interactions (technical, administrative, and abuse contacts) are handled by DISA Columbus (Defense Information Systems Agency) on NNIC's behalf, and the abuse address on file is disa.columbus.ns.mbx.arin-registrations@mail.mil. The key triage point is that AS139 is dormant at the routing level: as of June 2026 it originates zero IPv4 and zero IPv6 prefixes, has zero observed BGP peers, upstreams, and customers, and is seen by none of RIPE's RIS collectors. It last appeared in the global routing table with prefix 140.178.0.0/16 on March 10, 2007, and first appeared with 192.31.147.0/24 on August 18, 2000. CAIDA ranks it at position 79,459, consistent with an inactive ASN. NNIC continues to hold dozens of other ASNs and active Navy IPv4 networks, but AS139 itself is best described as a legacy, currently-unused government ASN. No notable public abuse signal was found as of June 2026; it is absent from the Spamhaus ASN-DROP list and from the NANOG and BGP-incident archives reviewed.

Operator

Navy Network Information Center (NNIC), U.S. Department of Defense / U.S. Navy [Confirmed] — ARIN RDAP, bgp.he.net

Country / RIR

US, ARIN [Confirmed] — ARIN RDAP (block 1–1876, "Assigned by ARIN")

Allocated

ARIN ASN RegDate 1987-11-25 (ARIN registry event, NOT an IEEE/vendor date); autnum record last changed 2011-07-05; org record last changed 2025-03-13 [Confirmed for the shown dates] — rdap.arin.net/registry/autnum/139

Org status

active registrant (NNIC, via DISA Columbus); ASN dormant at routing level [Confirmed]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal as of 2026-06-13; absent from Spamhaus ASN-DROP (424-entry feed, AS139 not present); no NANOG/BGP-incident mentions found; Scamalytics tags the NNIC ISP "potentially low fraud risk" — spamhaus.org/drop/asndrop.json, seclists.org/nanog

Network & routing

Network type

U.S. military / government infrastructure; NNIC manages Navy IP space and ASNs across naval bases and operational units, but AS139 itself is routing-inactive [Confirmed]

Size

zero announced prefixes (IPv4 0 / IPv6 0), ~0 addresses currently routed; CAIDA customer cone = 1 ASN / 0 prefixes / 0 addresses — stat.ripe.net routing-status, CAIDA AS Rank (2026-06)

Routing/peering

inactive — 0 BGP peers, 0 upstreams, 0 customers, 0 observed neighbours; seen by 0/326 RIS peers (v4) and 0/319 (v6); last active prefix 140.178.0.0/16 (2007-03-10), first 192.31.147.0/24 (2000-08-18) [Confirmed] — stat.ripe.net, bgp.he.net

RPKI

Unknown — RIPEstat RPKI validation was skipped (no announced prefix to evaluate); no valid/invalid ROAs recorded at bgp.he.net [Unknown]

Peering policy

no PeeringDB record for AS139; not actively routing, so none published [Unknown] — peeringdb.com (no entry), bgp.he.net

AS rank

CAIDA position 79,459; clique member = false [Confirmed] — api.asrank.caida.org

Notable usage

one of the oldest ASNs (registered 1987); NNIC holds many ASNs and active Navy IPv4 networks, but AS139 is currently unused at the routing level — navy.mil is the associated domain [Likely for navy.mil; Confirmed for legacy/NNIC]

IXP presence

none detected [Confirmed] — CAIDA AS Rank (ixp=null), bgp.he.net

Admin/abuse contact

DISA Columbus — Registration, 300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 [Confirmed] — ARIN RDAP, stat.ripe.net abuse-contact-finder

Registered address

2465 Guadalcanal Road, Building 1265, Virginia Beach, VA 23459, US [Confirmed] — ARIN RDAP

Related

other NNIC/DoD ASNs (e.g., AS22 has an "Open" PeeringDB policy); NNIC also manages Navy networks such as 164.190.0.0/16 and 164.191.0.0/16 [Likely]

Analyst note

Encountered as a legacy DoD/Navy ASN. WHOIS resolves to NNIC (managed by DISA Columbus); registration date 1987 is an ARIN event. Clean but dormant — verify before any "active transit" assumption.