Autonomous system detail

AS732

Not announced

Operated by AFCONC-BLOCK2-AS - Air Force Systems Networking.

Summary

// analyst note
AS732 has no individual ARIN autnum object; it is covered by a shared 20-ASN block (AS727-AS746) registered to Air Force Systems Networking. Dormant since 2012-09 per RIPEstat/CAIDA/bgp.he.net. allocated_date left null: ARIN's top-level events[] array for the block carries only a last-changed timestamp (2008-06-06) and no registration event; the 2008-06-05 (org 7ESG) and 2009-06-24 (POC REGIS10-ARIN) dates belong to nested entity records, not the autnum, and are not the block's allocation date.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-25 in reachable sources (bgp.he.net, ipinfo.io); AbuseIPDB/Talos/Spamhaus lookups errored (403/403/404) and were not checked.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS732 is a dormant US Department of Defense autonomous system, registered under ARIN to Air Force Systems Networking, that currently announces zero IPv4 and zero IPv6 prefixes — it has not appeared in the global routing table since 2012.

AS732 has no individual ARIN autnum record of its own. RDAP lookup returns a shared 20-ASN block (handle AS727, name AFCONC-BLOCK2-AS) spanning AS727–AS746, registered to Air Force Systems Networking. The registrant entity, 7ESG, is based at Maxwell Air Force Base, Alabama; administrative, technical, and abuse contact routes through DISA-Columbus, Ohio. This points to a Department of the Air Force / DoD-administered allocation rather than a commercial network operator.

Routing data from RIPEstat and CAIDA agree the ASN is completely inactive: 0 announced IPv4/IPv6 prefixes, a CAIDA AS rank of 79,459, a singleton customer cone (0 downstream prefixes, 0 addresses), and zero observed upstreams or peers. Hurricane Electric's historical BGP data shows AS732 last originated a prefix — 186.250.74.0/23 — for roughly three months in 2012 before going silent. That prefix's WHOIS traces to an unrelated Brazilian entity, and bgp.he.net flags it as a bogon announcement.

ARIN publishes no allocation date for this block record: the top-level events[] array for AS727-AS746 contains exactly one entry — a "last changed" event dated 2008-06-06 — and no registration event. Two dates found elsewhere in the RDAP response, 2008-06-05 (the registrant org 7ESG) and 2009-06-24 (POC REGIS10-ARIN), belong to nested entity records, not the autnum itself, and are not the block's allocation date. allocated_date is recorded Unknown accordingly.

Operator
Air Force Systems Networking (US Department of the Air Force / DoD; ARIN block registrant entity 7ESG, Maxwell AFB, AL) [Confirmed] — ARIN RDAP autnum block AS727-AS746, https://rdap.arin.net/registry/autnum/732
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP
Allocated
Unknown — the block's RDAP top-level events[] carries only a "last changed" event (2008-06-06), no top-level registration event; an entity-nested date (2008-06-05) exists but is a decoy, not the autnum's own registration date
[Confirmed] — ARIN RDAP autnum top-level events, https://rdap.arin.net/registry/autnum/732. Last changed: 2008-06-06 [Confirmed]
Org status
ARIN RDAP status "active" for the AS727-AS746 block as of last-changed 2008-06-06, but AS732 itself has not routed since 2012 — registered/active at the RIR level while operationally dormant [Confirmed] — ARIN RDAP
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (admin/tech/abuse, 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] — ARIN RDAP, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 in reachable sources (bgp.he.net, ipinfo.io); AbuseIPDB, Talos, and Spamhaus lookups returned errors (403/403/404) and could not be checked. One historical bogon-flagged announcement (186.250.74.0/23, 2012) is unresolved, not confirmed malicious

[Likely] — bgp.he.net/AS732

Network & routing

Network type
US government / military network (Department of Defense — Department of the Air Force), administered via DISA-Columbus as ARIN point of contact; not a commercial network [Likely] — ARIN RDAP
Size
dormant — 0 IPv4 prefixes / 0 addresses currently announced, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank (2026-07)
Routing/peering
NOT currently announced; 0 observed upstreams and 0 observed peers (CAIDA asnDegree); last visible in the global routing table 2012-09-06 (RIPEstat routing-status last_seen; first_seen 2012-06-16), briefly originating 186.250.74.0/23 (2012-06 to 2012-09) [Confirmed]. No PeeringDB record exists (404); no public peering policy found
[Unknown] — bgp.he.net/AS732, peeringdb.com/asn/732
RPKI
not applicable — AS732 announces no prefixes, so there are no ROAs to validate [Confirmed]
Notable usage
no independent sourcing found describing notable usage specific to AS732; it sits within a US Air Force-administered ASN block (AS727-AS746) [Unknown] — ARIN RDAP
Related ASNs
sibling ASNs within the same ARIN block AS727-AS746 (handle AS727, "AFCONC-BLOCK2-AS"), all registered to Air Force Systems Networking [Confirmed] — ARIN RDAP
Analyst note
AS732 has no individual ARIN autnum object — it is covered by a shared 20-ASN block registered to Air Force Systems Networking (US Air Force/DoD). Completely dormant since 2012; all routing sources agree on zero current announcements. allocated_date is Unknown: ARIN's top-level events[] for the block carries only a last-changed timestamp (2008-06-06) and no registration event; the 2008-06-05 and 2009-06-24 dates belong to nested entity records, not the autnum, and do not resolve to an allocation date.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.