AS493

AS493 sits inside a large ARIN block registration, AFCONC-BLOCK1-AS, spanning AS379 through AS508 and assigned as a single unit to Air Force Systems Networking (org handle 7ESG), a U.S. Department of the Air Force / Department of Defense numbering resource administered through DISA Columbus, Ohio. ARIN's RDAP record for the containing autnum object shows a top-level registration event dated August 4, 1989, with the block last changed June 6, 2008 — there is no AS493-specific sub-record separate from the block. The ASN is not currently visible in the global routing table: RIPEstat's as-overview reports announced:false, and RIS BGP data shows zero of 327 IPv4 peers and zero of 321 IPv6 peers currently seeing it. Historical routing data places two prefixes under AS493's origin — 137.95.31.0/24 first seen November 29, 2018, and 137.95.60.0/24 last seen May 6, 2021 — after which the ASN dropped out of the default-free zone. CAIDA AS Rank corroborates the dormancy, ranking AS493 79,459th globally with a customer cone limited to itself (zero downstream prefixes or ASNs) and zero observed provider, peer, or customer relationships. No PeeringDB network object exists for AS493 (a 404 on api/net?asn=493), and no notable public abuse or security signal was found across Spamhaus, abuse.ch, and NANOG archive searches — consistent with an inactive, legacy DoD-held numbering block rather than an actively operated or abused network.

Operator

Air Force Systems Networking (U.S. Dept. of the Air Force / DoD; ARIN org handle 7ESG, admin/abuse/technical via DISA-Columbus, OH) [Confirmed] — https://rdap.arin.net/registry/autnum/493

Country / RIR

US, ARIN [Confirmed] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=493

Allocated

1989-08-04 (ARIN registry top-level autnum registration event, covering the containing AFCONC-BLOCK1-AS block, AS379–AS508); last changed 2008-06-06 [Confirmed] — https://rdap.arin.net/registry/autnum/493

Org status

active per ARIN RDAP (status: active); block administered through DISA Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/493

Contacts

admin/abuse/technical via REGIS10-ARIN, DISA-Columbus, 300 North James Road, Whitehall, OH 43213; email disa.columbus.ns.mbx.arin-registrations@mail.mil; registrant org 7ESG at 501 East Moore Dr. Bldg 884 Rm 1100 Gunther Annex, Maxwell AFB, AL 36114

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

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-10 — checked Spamhaus DROP/SBL, abuse.ch URLhaus, NANOG archives, IPQualityScore; consistent with an inactive legacy DoD block

Network & routing

Network type

U.S. military/government (Department of the Air Force) internal numbering block, not a commercial ISP/IXP/CDN [Likely] — https://rdap.arin.net/registry/autnum/493

Size

dormant — 0 IPv4/IPv6 prefixes currently announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/493, https://stat.ripe.net/data/routing-status/data.json?resource=493

Routing/peering

NOT announced — 0/327 v4 RIS peers and 0/321 v6 RIS peers see it; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB record exists (404) [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=493, https://www.peeringdb.com/api/net?asn=493

RPKI

not assessable — no prefixes currently announced, so RIPEstat's rpki-validation endpoint has no specific prefix to query [Unknown] — https://stat.ripe.net/data/rpki-validation/

Notable usage

historically originated 137.95.31.0/24 (first seen 2018-11-29) and 137.95.60.0/24 (last seen 2021-05-06) before dropping out of the DFZ; no first-party usage description found beyond the registry name [Confirmed for routing history; Unknown for usage narrative] — https://stat.ripe.net/data/routing-status/data.json?resource=493

Related ASNs

within the AFCONC-BLOCK1-AS block registration, AS379–AS508, all held by the same org (7ESG, Air Force Systems Networking) [Confirmed] — https://rdap.arin.net/registry/autnum/493

Analyst note

RDAP resolves AS493 to a block-level autnum object (handle AS379, startAutnum 379, endAutnum 508) rather than an AS493-specific record; two independent research angles (operator-official and routing) both read the same top-level registration event (1989-08-04), corroborated by security and community angles — recorded as allocated_date per project convention, not nulled.