Autonomous system detail

AS733

Not announced

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

Summary

// analyst note
AS733 is not individually delegated in ARIN RDAP — it falls inside the consolidated block AS727-746 (AFCONC-BLOCK2-AS), registered to Air Force Systems Networking and administratively serviced by DISA-Columbus. The block's top-level RDAP events[] carries only a last-changed event (2008-06-06), no registration event, so allocated_date is recorded null rather than substituting nested entity-level dates (org 2008-06-05, POC 2009-06-24) that describe those records, not AS733 itself. All routing sources agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-25; not in NANOG mailing-list archives; bgp.he.net and ipinfo.io show it unrouted/inactive.
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

AS733 is a dormant, U.S. Air Force/DISA-administered autonomous system number that currently announces zero IPv4 and zero IPv6 prefixes in the global routing table. It is not individually delegated in ARIN's records; instead it falls inside the consolidated block AS727-746 ("AFCONC-BLOCK2-AS"), registered to Air Force Systems Networking (org handle 7ESG) at Maxwell AFB, Alabama.

Because AS733 sits inside a block-level RDAP object rather than its own autnum record, no ASN-specific allocation date could be confirmed. The block's top-level RDAP events array carries only a single "last changed" entry (2008-06-06); nested entity-level dates for the registrant org (2008-06-05) and the DISA-Columbus point of contact (2009-06-24) describe those records, not AS733's own registration, so they are not recorded as its allocated_date.

Administratively, AS733 is serviced by DISA-Columbus (Defense Information Systems Agency), whose Registration group (handle REGIS10-ARIN) holds the abuse/admin/tech contact role and is confirmed as the sole abuse contact in RIPEstat as well. No dedicated public website, peering-policy page, or PeeringDB network record exists for AS733, consistent with internal or non-publicly-routed DoD use rather than a live commercial network.

Routing visibility is unanimous across sources: CAIDA AS Rank places it at 79,459 with a singleton customer cone (0 prefixes, 0 addresses), RIPEstat shows 0 of 331 v4 and 0 of 324 v6 RIS peers observing it, and bgp.he.net corroborates 0 announced prefixes and 0 BGP peers. RPKI posture cannot be assessed because there are no announced prefixes to validate against ROAs.

Operator
Air Force Systems Networking (ARIN registrant org, handle 7ESG); administratively serviced by DISA-Columbus (POC handle REGIS10-ARIN) [Confirmed] — ARIN RDAP entity/7ESG, entity/REGIS10-ARIN
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP registrant address (Maxwell AFB, AL)
Allocated
Unknown — the consolidated block AS727-746 containing AS733 has no autnum-level "registration" event in its RDAP events[]; only a "last changed" event dated 2008-06-06 is present (live re-fetch confirmed, not a truncation artifact). Nested entity registration dates (org 2008-06-05, POC 2009-06-24) describe those records, not AS733's own allocation.
[Confirmed] — ARIN RDAP autnum/733
Org status
active per ARIN (status "active" on the AS727-746 block containing AS733) [Confirmed] — ARIN RDAP autnum/733
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext2; 300 North James Road, Whitehall, OH 43213 (REGIS10-ARIN, DISA-Columbus Registration group) [Confirmed] — ARIN RDAP entity/REGIS10-ARIN, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not in NANOG mailing-list archives; bgp.he.net/ipinfo.io show it unrouted/inactive. Spamhaus and Talos status Unknown (403 on automated fetch, not confirmed clean) [Confirmed for NANOG/bgp.he.net; Unknown for Spamhaus/Talos]

Network & routing

Network type
U.S. DoD/Air Force network infrastructure administered through DISA Columbus, OH; currently unrouted [Likely] — ARIN RDAP entity records
Size
dormant — 0 IPv4/IPv6 announced prefixes, 0 addresses; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA ASRank, bgp.he.net (2026-07)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/331 v4, 0/324 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network record exists for ASN 733 [Confirmed]
RPKI
not assessable — AS733 announces no prefixes, so there are no ROAs to validate [Confirmed] — RIPEstat rpki-validation (skipped, no prefix supplied)
Notable usage
not observed originating routes on the public Internet; consistent with internal/non-publicly-routed DoD use or a dormant/reserved slot within the AS727-746 block [Confirmed] — bgp.he.net/AS733
Related ASNs
AS727-746 ("AFCONC-BLOCK2-AS"), the consolidated block AS733 sits inside [Confirmed] — ARIN RDAP autnum/733
ASN
AS733 [Confirmed] — ARIN RDAP autnum/733
Analyst note
AS733 is block-registered (not individually delegated) inside AS727-746, a DoD/Air Force allocation with zero live routing; the allocation date is genuinely absent from the block's top-level RDAP events, not merely unconfirmed — recorded null rather than substituted from decoy entity dates.
[ 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.