AS734

AS734 is a dormant, unannounced autonomous system number registered to the U.S. Air Force — specifically to registrant handle 7ESG, "Air Force Systems Networking" — and administered on the registration side by DISA-Columbus. As of 2026-07-25 it originates zero IPv4 and zero IPv6 prefixes anywhere in the global routing table, making it a dark government block rather than an actively operated network.

The ASN sits inside ARIN's consecutive block AS727-AS746 (handle AFCONC-BLOCK2-AS), which has no separate per-ASN RDAP record of its own for AS734. No PeeringDB network entry exists for this ASN, and no external corroboration from bgp.he.net or bgp.tools beyond confirming zero visible relationships was obtained.

Routing sources agree unanimously: CAIDA AS Rank places it at 79,459, with a customer cone of a single ASN (itself, 0 prefixes, 0 addresses) and zero customer, peer, or provider relationships. RIPEstat's route-collector visibility shows 0 of 331 IPv4 peers and 0 of 324 IPv6 peers observing this AS, consistent with complete routing inactivity. Because it announces no prefixes, RPKI status is not assessable — there are no route objects to validate against any ROA.

Operator

Air Force Systems Networking (ARIN registrant handle 7ESG; US Air Force / DoD), administered on the registration side by DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/734

Country / RIR

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

Allocated

Unknown — the RDAP autnum object's top-level events[] carries only a "last changed" event (2008-06-06), no top-level "registration" event; entity-nested dates (7ESG 2008-06-05, REGIS10-ARIN 2009-06-24) are registrant/contact record dates, not the autnum's own allocation date [Unknown for allocated_date; Confirmed for last_updated 2008-06-06] — https://rdap.arin.net/registry/autnum/734

Org status

active per ARIN RDAP registration (block AS727-AS746, AFCONC-BLOCK2-AS), but dormant/unannounced in the public routing table [Confirmed] — https://rdap.arin.net/registry/autnum/734

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil; entity REGIS10-ARIN ("Registration"), DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/734

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not in NANOG mailing-list archives or general web search; Spamhaus and Talos could not be directly queried (403/JS-gated), so treat as a tooling gap rather than a confirmed-clean result from those feeds

Network & routing

Network type

Government/military (US DoD — US Air Force); ASN falls within ARIN's consecutive block AS727-AS746 (AFCONC-BLOCK2-AS), which has no distinct per-ASN RDAP record [Confirmed] — https://rdap.arin.net/registry/autnum/734

Size

dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes currently routed; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — https://asrank.caida.org/asns/734, RIPEstat routing-status

Routing/peering

NOT announced — 0 of 331 RIS peers seeing it (v4), 0 of 324 (v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB net record [Confirmed] — https://asrank.caida.org/asns/734, https://www.peeringdb.com/api/net?asn=734

RPKI

not assessable — AS734 announces no prefixes, so there are no route objects to validate against a ROA [Confirmed] — RIPEstat rpki-validation for resource 734

Notable usage

none observed — 0 originated prefixes, 0 BGP peers on bgp.he.net; part of a US Air Force block but not currently visible in the public routing table [Confirmed] — https://bgp.he.net/AS734

Related ASNs

part of ARIN's consecutive block AS727-AS746 (AFCONC-BLOCK2-AS); sibling ASNs in that block share the same underlying registration [Confirmed] — https://rdap.arin.net/registry/autnum/734

Analyst note

research was constrained by an exhausted WebSearch budget across multiple angles, and the A5-community angle abstained entirely (no NANOG/Reddit/operator-reputation data). A2 and A3 disagreed on whether ARIN RDAP's top-level events[] carries a registration date for AS734; A3's more granular enumeration of the events array (explicitly distinguishing top-level vs. entity-nested dates) was treated as authoritative, so allocated_date is recorded as Unknown rather than the 2008-06-05 value A2 asserted.