AS720

AS720 (WR-LOGDIS-AS) is a legacy autonomous system registered under ARIN to Air Force Systems Networking, a U.S. Air Force / DISA-administered military network. Every routing source checked — RIPEstat and CAIDA AS Rank — agrees it announces zero IPv4 and zero IPv6 prefixes today, with zero visible BGP peers, so the triage-relevant fact is that this ASN is registered but dormant, not currently part of the public Internet routing table.

The registration itself dates to 1990-09-11, per the ARIN RDAP autnum's top-level registration event — not the newer 2008/2009/2025/2026 dates attached to the nested registrant-org and abuse-contact entities, which are unrelated database-housekeeping timestamps. The autnum was last updated 2011-08-11. RIR status is "active," meaning the record is valid and unretired, but that is a registry-status flag, not a routing signal.

CAIDA places AS720 at ASRank 79,459 with a customer cone of exactly one ASN — itself — and zero prefixes or addresses in that cone; provider, peer, and customer degree are all zero. No PeeringDB network object exists for AS720, and RIPEstat's RIS peer count shows 0 of roughly 328 IPv4 and 0 of roughly 324 IPv6 route collectors seeing it.

Because AS720 announces no prefixes, RPKI status cannot be assessed — there is nothing to validate ROAs against. Registrant contact resolves to Maxwell AFB, Alabama (Gunther Annex, 501 East Moore Dr., Bldg 884), while the ARIN abuse/admin/tech contact routes through DISA-Columbus in Whitehall, Ohio — the DoD's shared ARIN registration-services desk rather than a dedicated NOC for this specific ASN.

Operator

Air Force Systems Networking (U.S. Air Force / DISA-administered network; ARIN handle WR-LOGDIS-AS) [Confirmed] — https://rdap.arin.net/registry/autnum/720

Country / RIR

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

Allocated

1990-09-11 (top-level autnum registration event, ARIN RDAP); last changed 2011-08-11 [Confirmed] — https://rdap.arin.net/registry/autnum/720

Org status

RIR record active, but not present in the public DFZ — registered/reserved, not currently routed [Confirmed] — https://rdap.arin.net/registry/autnum/720, https://bgp.he.net/AS720

Contacts

abuse/admin/tech via disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, 300 North James Road, Whitehall, OH 43213); registrant address 501 East Moore Dr., Bldg 884, Rm 1100, Gunther Annex, Maxwell AFB, AL 36114 [Confirmed] — https://rdap.arin.net/registry/autnum/720

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25; bgp.he.net shows the ASN inactive and general web search surfaced nothing, but direct Spamhaus and Talos checks both returned HTTP 403 and are unverified

Network & routing

Network type

inferred U.S. government/military (Air Force) administrative network, based on registrant org name and DoD ARIN registration channel — not confirmed by an operator-published statement [Likely] — https://rdap.arin.net/registry/autnum/720

Size

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

Routing/peering

NOT announced — 0 RIS peers seeing it (0/328 v4, 0/324 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network object exists [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=720, https://www.peeringdb.com/api/net?asn=720

RPKI

not assessable — AS720 announces no prefixes, so there are no ROAs to validate [Unknown/not applicable] — https://stat.ripe.net/AS720

Notable usage

Unknown — no operator-published description found; current BGP inactivity suggests internal/reserved DoD use rather than a public-facing announced network [Unknown]

Related ASNs

Unknown — no other Air Force/DoD ASNs confirmed as related this session (WebSearch budget exhausted) [Unknown]

Analyst note

Dormant legacy DoD ASN registered 1990-09-11, registry-active but unrouted since at least its 2011 update. No PeeringDB entry and no confirmed operator website (af.mil and afmc.af.mil both returned HTTP 403 to fetch attempts); Spamhaus/Talos abuse checks were also 403'd and remain unverified.