Autonomous system detail  ·  US flag US

AS796

Not announced

Last known operator AT&T Services, Inc. No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Shared-block legacy ASN (AS795-797, AMERITECH-AS) registered to AT&T Services, Inc. All routing sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero announcements, zero peers, zero cone. AS796 is outside AT&T's published peering policy (AS7018/AS2685-2688). NANOG mailing-list archives and general web queries were searched; no operator-reputation or outage-report evidence was found.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-08-01; Spamhaus check.spamhaus.org blocked automated access (403) so ASN-DROP listing status is Unknown, not confirmed clean.
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  ·  9 sources  ·  How this page is checked

AS796 is a dormant legacy ASN registered to AT&T Services, Inc. under the historical Ameritech block name that announces zero prefixes today. It is registry-active but carries no live routing.

The ASN was never registered individually. ARIN's RDAP autnum object for AS796 is a range record, handle AS795, spanning AS795 through AS797, all three assigned together to AMERITECH-AS. The block's top-level registration event dates to 1990-12-13, with a last-changed event of 2012-04-02; ARIN does not expose a per-ASN sub-date within a range block.

Every routing source checked agrees on complete inactivity: RIPEstat shows 0 announced IPv4 and IPv6 prefixes with 0 of 328 RIS peers seeing it in v4 and 0 of 322 in v6. CAIDA AS Rank places it at 79,459 with seen=false, and its customer cone is a singleton — itself, 0 prefixes, 0 addresses. bgp.he.net and bgp.tools corroborate zero peers and zero hosted domains.

AS796 is outside AT&T's public peering program. The company's published peering policy (corp.att.com/peering) scopes only to AS7018 (US), AS2685 (Canada), AS2686 (EMEA), AS2687 (Asia-Pacific), and AS2688 (Latin America); AS796 is not listed, and PeeringDB has no network record for it. AS7018 — AT&T's actively peered, Selective-policy ASN — is a distinct network and should not be conflated with AS796.

RPKI posture cannot be assessed: with no announced prefixes there are no ROAs to validate. No notable public abuse signal was found as of 2026-08-01, though Spamhaus's own lookup page blocked automated access, leaving that one specific check genuinely unresolved rather than confirmed clean.

Exposure
none identified — AS796 announces no prefixes and has no observed BGP peers, so there is no live routed address space to attack or hijack.
Abuse signal
no notable public abuse reports found as of 2026-08-01 across NANOG archives and general web queries; consistent with an unrouted ASN generating no live traffic.
Spamhaus status
Unknown — check.spamhaus.org returned HTTP 403 to automated fetch, so ASN-DROP listing status could not be directly confirmed and should not be assumed clean.
Peering scope
AS796 falls outside AT&T's published peering policy (AS7018/AS2685-2688 only) and has no PeeringDB net record, so it carries no active peering-relationship exposure.
Operator
AT&T Services, Inc. (registrant org for ARIN block AS795–AS797, named "AMERITECH-AS"; legacy Ameritech, a Regional Bell Operating Company later absorbed into SBC/AT&T) [Confirmed] — ARIN RDAP
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP, RIPEstat
Allocated
1990-12-13 (ARIN RDAP top-level "registration" event for the shared AS795–797 block; ARIN does not expose a per-ASN sub-date within the range); last changed 2012-04-02 [Confirmed] — ARIN RDAP autnum top-level events
Org status
ARIN registry status active (block not revoked/reserved) but operationally dormant — zero routes announced [Confirmed] — ARIN RDAP, bgp.he.net
Contacts
abuse@att.net; RDAP entity records list Indianapolis, IN (registrant / admin-tech POC), Plano, TX (abuse POC), and Middletown, NJ (routing POC) — these are contact-record addresses, not the ASN's operating geography [Confirmed for abuse contact; Likely for POC addresses]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-08-01 — not in NANOG archive searches or general abuse-feed queries; Spamhaus check.spamhaus.org blocked automated access (403), so ASN-DROP listing status is Unknown, not confirmed clean [Likely for absence of general signal; Unknown for Spamhaus specifically]

Network & routing

Network type
legacy/dormant ASN; originally issued to Ameritech, registrant of record is now AT&T Services, Inc. following the SBC/AT&T/Ameritech consolidation; announces 0 IPv4/IPv6 prefixes — registry-active but not in production use [Confirmed] — bgp.he.net, ipinfo.io
Size
dormant — 0 IPv4 prefixes / 0 IPv4 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-08)
Routing/peering
NOT announced — 0 of 328 RIS peers seeing it in v4, 0 of 322 in v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB net record for AS796; AT&T's published peering policy (corp.att.com/peering) scopes only to AS7018/AS2685/AS2686/AS2687/AS2688 — AS796 is not among them [Confirmed]
RPKI
not assessable — AS796 announces no prefixes, so there are no ROAs to validate [Confirmed] — stat.ripe.net
Notable usage
none found — bgp.he.net and ipinfo.io both show 0 announced prefixes, 0 peers, 0 hosted domains; contrast note: AT&T's primary actively-peered ASN is AS7018 (Selective policy, PeeringDB net 674), a distinct network from AS796 [Confirmed]
Related ASNs
AS795 and AS797 (same ARIN block, AMERITECH-AS); AS7018 (AT&T's actively peered primary ASN — different network, not part of the AS795-797 block) [Confirmed]
Analyst note
shared-block legacy ASN encountered with no AS796-specific operator page; findings rest on ARIN RDAP, RIPEstat, CAIDA ASRank, bgp.he.net, bgp.tools, ipinfo.io, NANOG mailing-list archive searches, and AT&T's own peering-policy page — no operator-reputation or outage-report evidence was found.
[ 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.