AS729

AS729 is a dormant, unannounced autonomous system registered under ARIN to Air Force Systems Networking (registrant entity 7ESG), a U.S. Department of Defense network resource administered through DISA-Columbus rather than a commercial operator. Live routing data shows zero IPv4 and zero IPv6 prefixes originated as of 2026-07-25.

The ASN sits inside AFCONC-BLOCK2-AS, an ARIN block spanning AS727 through AS746 — a pattern typical of consecutively allocated DoD ASN ranges rather than a standalone commercial assignment. No public operator website, peering policy page, or PeeringDB listing exists for AS729; a direct PeeringDB API query returned no result.

Routing visibility is uniformly empty across sources: 0 of 331 RIS peers see an IPv4 route and 0 of 324 see an IPv6 route, CAIDA reports zero customer, peer, and provider degree, and the customer cone is a singleton (itself, 0 prefixes, 0 addresses). RPKI posture cannot be assessed because nothing is announced, so there are no ROAs to validate.

The RDAP autnum record's top-level events array carries only a "last changed" entry (2008-06-06) with no "registration" eventAction present at that level; entity-level registration dates on the containing block and registrant objects exist but are not the autnum's own top-level registration event, so the allocation date is recorded here as unresolved rather than invented.

Exposure

AS729 is unrouted (0 announced prefixes), so it presents no live attack surface via BGP-visible address space today.

Abuse signal

No notable public abuse signal found as of 2026-07-25 across bgp.he.net, ipinfo.io, bgp.tools, and a honeypot/threat-intel listing site — but this is absence-of-evidence, not a confirmed clean record.

Feed gaps

Spamhaus ASN lookup returned HTTP 403 (access-gated) and AbuseIPDB's AS729 page returned HTTP 404; both are recorded Unknown rather than checked-and-clean.

RPKI

Not assessable — zero originated prefixes means no ROAs exist to validate against.

Operator

Air Force Systems Networking (ARIN registrant entity 7ESG); U.S. Department of Defense network resource administered via DISA-Columbus [Confirmed] — ARIN RDAP autnum/729, entity/7ESG

Country / RIR

US, ARIN [Confirmed] — ARIN RDAP autnum/729

Allocated

Unknown — the autnum's top-level RDAP events[] array contains only one entry, eventAction "last changed" (2008-06-06); no "registration" eventAction is present at the top level (entity-level dates on the containing block/registrant objects are not the autnum's own registration event)

[Confirmed absence] — https://rdap.arin.net/registry/autnum/729

Org status

active [Confirmed] — ARIN RDAP autnum/729

Contacts

DISA-Columbus, 300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil [Confirmed] — ARIN RDAP autnum/729

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 across bgp.he.net, ipinfo.io, bgp.tools, jamesbrine.com.au; Spamhaus (403) and AbuseIPDB (404) could not be directly verified and are recorded Unknown, not clean

Network & routing

Network type

government/military network (U.S. Air Force), not a commercial ISP or content network [Likely] — ARIN RDAP autnum/729

Size

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

Routing/peering

NOT announced — 0/331 RIS peers see it on IPv4, 0/324 on IPv6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB listing (API query returned no result) [Confirmed]

RPKI

not assessable — AS729 announces no prefixes, so no ROAs exist to validate [Confirmed]

Notable usage

Unknown — no sourced public information found [Unknown]

Related ASNs

AS727–AS746 (AFCONC-BLOCK2-AS, the ARIN block AS729 falls within) [Confirmed] — ARIN RDAP autnum/729

Analyst note

Dormant DoD/USAF ASN within a consecutively-allocated Air Force ASN block; unrouted with zero BGP visibility across all sources checked. Top-level RDAP registration date is genuinely absent from the autnum object, distinct from decoy entity-level event dates (registrant 2008-06-05, later entity registration 2009-06-24) that do not belong to the autnum itself.