Autonomous system detail

AS507

Not announced

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

Summary

// analyst note
AS507 has no standalone RDAP record; it resolves to the shared AS379-AS508 block (AFCONC-BLOCK1-AS). Dormant/unrouted except one brief announcement of 103.168.8.0/24 (2021-10-03 to 2021-10-06). A single-source claim (PeeringDB org page) of roughly 962,048 IPv4 addresses for the parent org conflicts with the 0 currently-announced addresses and was not independently corroborated — recorded as Unknown pending confirmation, not asserted as AS507's own address space.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-10; partial Spamhaus ASN-DROP check (header only), zero NANOG MARC archive hits for 'AS507', no threat-intel/hijack writeups found.
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

AS507 is a legacy autonomous system number registered under ARIN inside the block AS379AS508, a single contiguous RDAP record named AFCONC-BLOCK1-AS. ARIN's own object for this range shows registrant entity 7ESG, "Air Force Systems Networking," at Maxwell AFB, Alabama, with administrative, technical, and abuse duties delegated to DISA-Columbus in Whitehall, Ohio. The block's top-level registration event dates to 1989-08-04, with a last-changed timestamp of 2008-06-06 — a first-party ARIN RDAP fact drawn from the autnum object itself, distinct from the newer 2008 and 2009 registration dates attached to the nested 7ESG and REGIS10-ARIN entity/contact records, which are decoys for this purpose. AS507 carries RDAP status "active" but is not currently routed: RIPEstat shows zero announced IPv4 or IPv6 prefixes and zero of 327/321 RIS peers seeing it. Its only observed routing history is a brief three-day announcement of 103.168.8.0/24 in October 2021. CAIDA places it at AS-rank 79,459 with a singleton customer cone (0 prefixes, 0 addresses) and zero peer/customer/provider degree — consistent with a dormant U.S. Air Force/DoD legacy allocation rather than an actively operated commercial network. No public abuse signal, NANOG discussion, or independent AS507-specific PeeringDB network listing was found.

Operator
Air Force Systems Networking (AFSN), U.S. Air Force / DoD; administratively grouped under ARIN block AS379–AS508 (RDAP name AFCONC-BLOCK1-AS); registrant entity 7ESG at Maxwell AFB, AL; admin/technical/abuse handled by DISA-Columbus (REGIS10-ARIN)
[Confirmed] — https://rdap.arin.net/registry/autnum/507
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1989-08-04 (ARIN RDAP autnum top-level registration event for block AS379–AS508); last changed 2008-06-06 [Confirmed] — https://rdap.arin.net/registry/autnum/507
Org status
active (RDAP status) legacy allocation; not independently delegated — RDAP resolves any ASN queried in AS379–AS508 to the same AS379 handle/block name [Confirmed] — https://rdap.arin.net/registry/autnum/507
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext. 2 (REGIS10-ARIN, DISA-Columbus, 300 North James Road, Whitehall, OH 43213); registrant org (7ESG) address 501 East Moore Dr., Bldg 884, Rm 1100, Gunther Annex, Maxwell AFB, AL 36114
[Confirmed] — https://rdap.arin.net/registry/autnum/507

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-10 — a spot-check of Spamhaus ASN-DROP returned only the file header (partial check, not exhaustive), zero hits for "AS507" in the NANOG MARC mailing-list archive, and no threat-intel/hijack writeups were found; consistent with a dormant, unrouted legacy allocation

[Likely] — https://www.spamhaus.org/drop/asndrop.txt, https://marc.info/?l=nanog&s=AS507

Network & routing

Network type
U.S. federal/military network; part of the wider Air Force Systems Networking mission portfolio (AFNET/NIPRNet, AFNET-S/SIPRNet, JRSS) per af.mil-family sources, though this describes the parent AFSN organization rather than an AS507-specific statement
[Likely] — https://www.acc.af.mil/About-Us/Fact-Sheets/Display/Article/1595271/air-force-network-integration-center/
Size
dormant — 0 IPv4/IPv6 prefixes currently announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA ASRank (2026-07)
Routing/peering
NOT currently announced — 0/327 v4 and 0/321 v6 RIS peers seeing it; CAIDA degree total 0 (customer/peer/provider all 0); one brief historical announcement of 103.168.8.0/24 (2021-10-03 to 2021-10-06, ~3 days); no PeeringDB network record for AS507 itself (peeringdb.com/asn/507 returns 404, confirmed live), though an org-level PeeringDB entry for "Air Force Systems Networking" (org ID 20118) exists — its relationship to AS507 specifically is unverified (single-source) [Confirmed for routing/RIS data; Likely/conflicting for the PeeringDB org linkage] — https://stat.ripe.net/data/routing-status/data.json?resource=507, https://www.peeringdb.com/asn/507, https://www.peeringdb.com/org/20118
RPKI
not assessable — AS507 announces no current prefixes, so there are no ROAs to validate [Confirmed] — RIPEstat rpki-validation (skipped, no prefix supplied)
Notable usage
sits inside the AFCONC-BLOCK1-AS range alongside dozens of other Air Force ASNs sharing the same registrant record (e.g. AS379, AS399, AS408, AS416, AS448, AS499); no independent traffic, IXP, or transit data found for AS507 specifically
[Likely] — https://rdap.arin.net/registry/autnum/507, https://ipinfo.io/AS379
Related ASNs
AS379, AS399, AS408, AS416, AS448, AS499 — other ASNs in the same AS379–AS508 block resolving to the same registrant [Confirmed for shared-block membership via RDAP; Likely for the specific sibling list per third-party lookups] — https://rdap.arin.net/registry/autnum/507, https://ipinfo.io/AS416
Analyst note
AS507 has no standalone RDAP record — it is one of many ASNs sharing the AS379–AS508 AFCONC-BLOCK1-AS block registered to Air Force Systems Networking. Dormant/unrouted at present aside from a brief 2021 announcement; no abuse signal found.
[ 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.