Autonomous system detail  ·  US flag US

AS742

Not announced

Last known operator Air Force Systems Networking. No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Dormant/unrouted DoD (Air Force Systems Networking) ASN within ARIN block AS727-AS746. All four routing sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero announcements, zero peers, zero cone. allocated_date is Unknown: the block's top-level RDAP events[] carries only a last-changed event (2008-06-06), and the 2008-06-05 date sometimes cited is a nested registrant-entity (7ESG) registration timestamp, not the autnum's own registration event; ipinfo.io's displayed 1970-01-01 date is a known epoch-placeholder artifact and was not used.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-27; not in a Spamhaus ASN-DROP spot-check, AbuseIPDB, or NANOG/seclists.org archives.
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  ·  7 sources  ·  How this page is checked

AS742 is a dormant, unrouted autonomous system number registered to Air Force Systems Networking, a U.S. Air Force/Department of Defense entity, that currently announces zero IPv4 and zero IPv6 prefixes in the global routing table. It is not an independent commercial network but a single number inside a larger federal block registration.

The ASN sits within ARIN's contiguous block AS727–AS746 ("AFCONC-BLOCK2-AS"), registered as a unit to Air Force Systems Networking (ARIN internal admin code 7ESG) at Maxwell AFB, Alabama, with registration and abuse-contact functions delegated to DISA-Columbus in Whitehall, Ohio. No individual operator website, About page, or peering-policy page exists for AS742 specifically — consistent with an internal DoD numbering resource rather than a public-facing operator.

Routing data from RIPEstat, CAIDA AS Rank, bgp.he.net, and bgp.tools agree unanimously: AS742 has 0 announced IPv4/IPv6 prefixes, 0 upstreams, 0 peers, and a CAIDA AS rank of 79,459 with a singleton customer cone (itself, 0 prefixes, 0 addresses). No PeeringDB network record exists for AS742 (a direct API query returned 404). Because nothing is announced, RPKI validation does not apply — there are no ROAs to check.

The ARIN RDAP record for the containing AS727–AS746 block carries only a top-level "last changed" event (2008-06-06) — there is no top-level registration event on this record. The 2008-06-05 timestamp sometimes read as an allocation date actually belongs to the nested registrant entity (7ESG, Air Force Systems Networking), not the autnum object itself; a separate point-of-contact entity (REGIS10-ARIN) carries its own 2009-06-24 registration date. Neither entity-level timestamp is the ASN's allocation date, so allocated_date is recorded here as Unknown. Separately, ipinfo.io displays a "1970-01-01" allocation date for AS742 — a Unix-epoch placeholder artifact, not a real event, and is not used here.

Exposure
AS742 announces no prefixes and has no observed BGP peers or upstreams, so it presents no live routed attack surface today.
Abuse signal
No notable public abuse listing found as of 2026-07-27 in a Spamhaus ASN-DROP spot-check (list fetch was truncated, so this is a spot-check, not exhaustive) or in general threat-intel searches — consistent with a dormant, unrouted federal block.
Community signal
No NANOG mailing-list or seclists.org archive threads referencing AS742 were found via targeted search; absence is expected for a non-public military allocation and is tagged Unknown rather than asserted as a confirmed negative.
Data-artifact caution
ipinfo.io's displayed "1970-01-01" allocation date for AS742 is a known epoch-placeholder artifact and should not be treated as a real registration event.
Operator
Air Force Systems Networking (U.S. Air Force / DoD entity; ARIN admin code 7ESG; Maxwell AFB, AL; registration/abuse contact desk via DISA-Columbus, Whitehall, OH) [Confirmed] — ARIN RDAP autnum record (rdap.arin.net/registry/autnum/742)
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP
Allocated
Unknown — the AS727–AS746 block's top-level RDAP events[] carries only a "last changed" event (2008-06-06); no top-level registration event exists on this record. The 2008-06-05 date belongs to the nested registrant entity (7ESG), not the autnum, and is not the allocation date
[Confirmed absence] — rdap.arin.net/registry/autnum/742
Org status
active per ARIN RDAP status field for the AS727–AS746 registration covering AS742 [Confirmed] — rdap.arin.net/registry/autnum/742
Contacts
abuse/registration handled by DISA-Columbus (disa.columbus.ns.mbx.arin-registrations@mail.mil); registrant address Maxwell AFB, AL [Confirmed] — RIPEstat abuse-contact-finder for resource 742, ARIN RDAP

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-27 — not in a Spamhaus ASN-DROP spot-check (list fetch truncated), AbuseIPDB, or general threat-intel searches; no NANOG/seclists.org archive threads found

[Likely — spot-check, not exhaustive] — spamhaus.org/drop/asndrop.txt, bgp.he.net/AS742

Network & routing

Network type
U.S. Air Force / DoD internal numbering resource within block AS727–AS746 ("AFCONC-BLOCK2-AS"); currently unrouted/dormant, not a commercial transit or access network [Confirmed] — ARIN RDAP, bgp.tools/as/742
Size
dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA AS Rank / bgp.he.net / bgp.tools (2026-07)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/329 v4, 0/324 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB record (404 on api/net?asn=742); no public peering policy found [Confirmed]
RPKI
not assessable — AS742 announces no prefixes, so there are no ROAs to validate [Confirmed] — RIPEstat rpki-validation for resource 742
Notable usage
single number within the AS727–AS746 block allocated as a unit to Air Force Systems Networking; no individually associated prefixes, peers, or upstreams currently in public routing data, consistent with an unused or reserved sub-allocation within the larger Air Force block
[Confirmed] — rdap.arin.net/registry/autnum/742, bgp.tools/as/742
Related ASNs
AS727–AS746 (the containing ARIN block registration, "AFCONC-BLOCK2-AS") [Confirmed] — rdap.arin.net/registry/autnum/742
Analyst note
Encountered as a dormant, unrouted ASN inside a U.S. Air Force/DoD block registration (AS727–AS746). No independent operator web presence, PeeringDB record, or routing activity exists for AS742 specifically; all four routing sources agree on zero announcements and zero peers. Allocated_date is recorded as Unknown: the block's top-level RDAP events[] carries only a last-changed event (2008-06-06), and the 2008-06-05 date some research angles cited is a nested entity-level registration timestamp (7ESG), not the autnum's own registration event — two angles reading that same entity date is not independent corroboration of an allocation fact.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-09-20 · one collector view, not a global census
// 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.