AS727

AS727 is a dormant U.S. Air Force / Department of Defense autonomous system, registered under ARIN to "Air Force Systems Networking" (org handle 7ESG), that currently announces zero IPv4 and zero IPv6 prefixes and shows no active BGP relationships.

The ASN sits inside a contiguous Air Force block, AFCONC-BLOCK2-AS, spanning AS727 through AS746. It is administered through ARIN by DISA Columbus rather than a self-published operator, with no dedicated public website found for "Air Force Systems Networking" — consistent with government/military infrastructure rather than a commercial ISP.

Every routing source consulted (RIPEstat, CAIDA AS Rank) agrees AS727 is unannounced: 0 of 331 RIS peers see it in IPv4, 0 of 324 see it in IPv6, and its CAIDA degree is 0 across customer, peer, and provider relationships. Its customer cone is a singleton — itself, 0 prefixes, 0 addresses — and its CAIDA AS rank sits at 79,459, near the bottom of the global ranking. No PeeringDB network record exists for AS727 (404 confirmed).

The RDAP autnum record's own top-level events array carries only a "last changed" entry dated 2008-06-06, with no "registration" eventAction present at that level. The nearby org-entity registration date (2008-06-05) belongs to the registrant organization object, not the autnum itself, so the true allocation date is recorded here as Unknown rather than substituted from that decoy field.

Operator

Air Force Systems Networking (ARIN Org ID 7ESG); U.S. Air Force / DoD network organization, not a standalone commercial entity [Confirmed operator identity; Likely for the DoD/military characterization] — rdap.arin.net/registry/autnum/727

Country / RIR

US, ARIN [Confirmed] — rdap.arin.net/registry/autnum/727

Allocated

Unknown — the autnum's own top-level events[] contains only a "last changed" entry (2008-06-06); no top-level "registration" eventAction exists. The nearby org-entity registration date (2008-06-05) is entity-level, not autnum-level, and was not substituted [Confirmed absence of a top-level registration event] — rdap.arin.net/registry/autnum/727

Org status

Active per ARIN RDAP [Confirmed] — rdap.arin.net/registry/autnum/727

Contacts

DISA Columbus (REGIS10-ARIN), 300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext.2. Registrant address: 501 East Moore Dr., Bldg 884 Rm 1100, Gunther Annex, Maxwell AFB, AL 36114 [Confirmed] — rdap.arin.net/registry/autnum/727

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not in Spamhaus botnet-controller list, abuse.ch, Talos reputation search, or NANOG-style archives; a 2023 Forbes report on an unrelated broader Air Force communications incident was found but not attributed to AS727 specifically

Network & routing

Network type

government/military (U.S. Air Force / DoD infrastructure), inferred; currently dormant/unannounced [Likely] — rdap.arin.net/registry/autnum/727

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat announced-prefixes/routing-status, CAIDA AS Rank (2026-07-26)

Routing/peering

NOT announced — 0/331 RIS peers see it in v4, 0/324 in v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network record (404) [Confirmed]

RPKI

not assessable — AS727 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation requires a prefix and was skipped [Unknown/not applicable]

Notable usage

Unknown — no independently verifiable description of specific traffic or usage patterns found beyond the ARIN registration record [Unknown]

Related ASNs

part of the contiguous AS727–AS746 "AFCONC-BLOCK2-AS" Air Force block [Confirmed for block range; Likely for individual member ASN details] — rdap.arin.net/registry/autnum/727

ASN / registry name

AS727, AFCONC-BLOCK2-AS [Confirmed] — rdap.arin.net/registry/autnum/727

Analyst note

Dormant U.S. Air Force/DoD ASN administered via ARIN by DISA Columbus; the autnum's RDAP top-level events carry no "registration" eventAction, only a "last changed" date, so allocated_date is left Unknown rather than fabricated from the nearby org-entity date. All routing sources agree on zero announcements, zero peers, zero cone.