Donate

AT&T Mobility network profile

US Mobile provider in United States. Wireless ASN footprint for handset and mobile data subscribers in the US.

AT&T Mobility is one of the major US Mobile providers tracked in this directory, with operations in United States. This profile page covers AT&T Mobility's primary ASN references (AS20057), common coverage locations, and the diagnostic context most useful when an IP lookup, ASN result, or traceroute attributes a public address to AT&T Mobility. Use it as a starting point for ASN, WHOIS, and reverse DNS validation rather than as a standalone proof of identity or location.

At a glance

Provider
AT&T Mobility
Category
US Mobile
Country/Region
United States
Known ASNs
AS20057

How to use this page

Use this profile when an IP lookup shows AT&T Mobility or a related ASN. It gives quick context before deeper routing and ownership checks.
  • Map the IP to ASN in the ASN lookup tool.
  • Validate reverse DNS and WHOIS ownership details.
  • Compare with blacklist status for reputation checks.

Common coverage locations

AT&T Mobility investigation notes

US mobile carriers commonly route traffic through shared gateways and carrier-grade NAT, which makes city-level precision weaker than the carrier and ASN match itself.

AT&T Mobility should be read as a mobile-gateway classification signal: city labels and hostnames are often rough network hints rather than exact device placement.

  • For mobile networks, broad geolocation and gateway-style hostnames are normal and should not be over-read.
  • Start with AS20057 as the expected ASN family before assuming the provider result is final.
  • When the decision is important, combine AT&T Mobility with reverse DNS, WHOIS / RDAP, and blacklist context instead of relying on one data source.

AT&T Mobility troubleshooting workflow

Start with IP to ASN mapping, then verify reverse DNS and WHOIS ownership. For email and abuse workflows, add blacklist checks to assess IP reputation signals around AT&T Mobility traffic.

AT&T Mobility: the wireless arm of the AT&T corporate family

AT&T Mobility is the wireless network operated by AT&T Inc., serving roughly 70 million postpaid and prepaid US wireless customers. The brand carries the direct lineage of Cingular Wireless, which AT&T renamed to AT&T Mobility after the 2007 corporate restructuring that consolidated SBC/AT&T’s wireless operations under the unified brand. Headquartered in Dallas, Texas, the wireless business shares corporate leadership and significant operational integration with the AT&T Internet wireline footprint that operates under the same parent company.

For IP attribution, AT&T Mobility is operationally distinct from AT&T Internet despite the shared brand. The two networks announce from different ASNs, serve different customer products, and produce different lookup signatures. An "AT&T" attribution alone is ambiguous between wireline residential broadband and wireless cellular - the disambiguation comes from the announcing ASN, which is the most consequential signal on AT&T-branded lookups. Investigators conflating the two AT&T networks routinely produce attribution errors that ASN-level checks would catch immediately.

AS20057 and the AT&T Mobility routing identity

The dominant ASN for AT&T Mobility wireless traffic is AS20057, registered as AT&T Mobility LLC. AS20057 announces the substantial majority of consumer cellular traffic exiting the wireless network and is the ASN most lookups will return for a typical AT&T cellular customer. The AT&T Internet Air fixed-wireless product, which uses the same underlying cellular infrastructure as consumer mobile customers, also announces through AS20057 - producing the artifact where AT&T residential fixed-wireless customers appear as wireless rather than as residential broadband regardless of the marketing label.

The wireless-only ASN structure makes AT&T Mobility attribution cleaner than the multi-tier AT&T Internet network. A lookup returning AS20057 is wireless or fixed-wireless; a lookup returning AS7018 is wireline AT&T Internet. The same household can produce both, depending on which device is being used at any moment, but the ASN signal disambiguates them reliably. Cross-checking through ASN Lookup identifies which AT&T product an IP represents in cases where the brand label alone is ambiguous.

CGNAT and packet-gateway architecture on AT&T Mobility

AT&T Mobility, like all major US wireless carriers, uses carrier-grade NAT to share IPv4 address space across the consumer mobile base. Smartphone customers and AT&T Internet Air subscribers both sit behind CGNAT, with public IPs representing hundreds or thousands of simultaneous subscribers depending on the gateway region. The packet-gateway concentration follows the standard wireless architectural pattern: regional aggregation points handle traffic from broad geographic catchments, producing geolocation results that map to the gateway region rather than to the physical subscriber location.

The CGNAT layer also affects port-related diagnostics. Inbound connections to AT&T Mobility addresses do not traverse the carrier NAT easily, peer-to-peer applications require relay servers or hole-punching techniques to function, and traditional port forwarding is unavailable. For AT&T Internet Air specifically, this is the most consequential difference from wireline AT&T Internet: a residential AT&T Fiber customer can host servers, forward ports, and run inbound services; an Internet Air customer of the same household has none of those capabilities because of the carrier NAT.

Cricket Wireless and the AT&T prepaid ecosystem

Cricket Wireless is AT&T’s prepaid brand, acquired from Leap Wireless in 2014 and operated as a fully owned subsidiary serving roughly 10 million customers. Cricket rides on the AT&T Mobility network and announces through the same wireless ASNs as the postpaid AT&T brand. From an IP attribution perspective, Cricket customers and AT&T postpaid customers are indistinguishable at the network layer - both appear as AT&T Mobility (AS20057), both share the same packet gateways, and both produce the same CGNAT-style behavior.

The dual-brand structure affects investigation work indirectly. A Cricket customer’s session and an AT&T postpaid customer’s session in the same metro produce indistinguishable IP signatures. For correlation across a single customer’s activity, account-level data from the specific brand (Cricket or AT&T) is required because the network layer cannot separate them. AT&T also operates additional prepaid lines under brands like Net10 (acquired through the TracFone transaction history) and partnerships with third-party prepaid resellers, all of which share the same network identity at the IP level.

AT&T Internet Air: the residential fixed-wireless product

AT&T Internet Air launched in 2023 as a residential fixed-wireless broadband product delivered over AT&T’s 5G cellular network. The product targets households where wireline AT&T Internet is unavailable or undesired, and has been deployed broadly across markets including major Texas metros, the Southeast US, and other regions where 5G coverage supports the product. The IP-level behavior is fully cellular: AS20057 routing, CGNAT, gateway-region geolocation, and minimal PTR records.

The lookup implication is that AT&T residential attribution can mean two structurally different products. An AT&T residential customer on AS7018 is on wireline Fiber, U-verse, or DSL. The same household on AS20057 is on Internet Air fixed- wireless. The ASN distinction is the cleanest disambiguator. For workflows that depend on service- tier specifics (upload capacity, IPv6 readiness, latency profile, port forwarding availability), the wireline-versus-wireless split is more consequential than any other AT&T-related distinction.

FirstNet and the federal-public-safety dimension

FirstNet is the nationwide public-safety wireless network operated by AT&T under a contract with the First Responder Network Authority, a federal entity created after the 9/11 Commission recommendations. FirstNet provides priority and preemptive cellular service to police, fire, EMS, and other emergency responders across the country, riding on AT&T’s commercial wireless infrastructure with dedicated spectrum (Band 14, 700 MHz) for high-priority traffic. FirstNet announces from AS22394in some configurations and AT&T Mobility ASNs in others, depending on the specific routing context.

The FirstNet presence on AT&T Mobility produces a specific lookup category that does not exist on other US wireless networks: addresses identified specifically as public-safety responder traffic. For investigation work, an attribution that suggests FirstNet traffic involves law-enforcement-related network usage by definition - a meaningfully different context than commercial cellular. Thefirstnet.comfamily of hostnames and specific FirstNet-allocated address blocks identify this traffic when it is visible at the lookup level, though most FirstNet activity is not externally distinguishable from standard AT&T Mobility usage without account-level context.

PTR conventions on AT&T Mobility

AT&T Mobility, like all major US wireless carriers, does not configure detailed reverse DNS on most consumer mobile ranges. The majority of AT&T cellular lookups return no PTR record or a generic carrier-owned hostname. Where PTRs exist, common patterns appear within themycingular.netdomain (a legacy identifier from the Cingular era still in use for some AT&T Mobility ranges) or under various att.netfamily subdomains for newer allocations. AT&T Internet Air ranges occasionally receive distinguishing PTR patterns but the practice is inconsistent.

The mycingular.net inheritance is operationally interesting because it survives in current PTRs more than fifteen years after the rebrand. A reverse DNS result containing mycingular.net identifies an AT&T Mobility address with high confidence and also dates the range to legacy Cingular-era provisioning. For investigation work, this is a useful range-age indicator. Newer AT&T Mobility allocations either have no PTR or use cleaner att.net-family naming, which makes them visually distinguishable from legacy ranges even when the ASN and traffic pattern are identical.

IPv6 deployment on AT&T Mobility

AT&T Mobility deployed native IPv6 to consumer cellular customers earlier than most carriers, with broad IPv6 support across LTE and 5G devices for many years. The architecture follows similar patterns to T-Mobile: IPv6 as the primary connectivity, IPv4 provided through carrier-side translation. AT&T Internet Air customers typically receive IPv6 through the same cellular mechanism as smartphone customers, with prefix delegation patterns that reflect cellular architecture rather than residential broadband defaults.

For privacy and VPN-related work, AT&T Mobility IPv6 readiness produces the same leak-surface characteristics as T-Mobile. A customer’s real network identity is dual-stack with IPv6 as the primary path. VPN clients that tunnel only IPv4 leave IPv6 traffic exiting through AT&T directly, producing visible leaks in our IPv6 leak test. The leak pattern is structural rather than configurational - any modern AT&T Mobility line has IPv6 to potentially leak unless the VPN client is specifically configured to capture it.

Investigation pitfalls on AT&T Mobility addresses

The largest specific limit on AT&T Mobility attribution is the standard mobile-network anonymity produced by CGNAT and packet-gateway concentration. A public IP represents thousands of simultaneous subscribers, and specific user attribution requires AT&T’s internal CGNAT mapping retrieved through proper legal process within the carrier’s retention window. AT&T retention windows for CGNAT mapping data are similar to other major US carriers - in the 30 to 90 day range typically, with longer retention for traffic associated with known investigations.

Specific AT&T Mobility second-order pitfalls include the Internet Air versus mobile ambiguity (same network, different customer products), the Cricket and prepaid sub-brand presence (multiple consumer brands sharing identical network infrastructure), and the FirstNet public-safety traffic category that occasionally surfaces in lookups. For investigations, treat AT&T Mobility attribution as a mobile-class signal requiring carrier-level mapping for specific attribution. The ASN distinguishes AT&T Mobility from AT&T Internet reliably; everything beyond that requires additional evidence to draw operational conclusions.

AT&T Mobility support and abuse handling paths

AT&T Mobility consumer support routes through the standard AT&T customer service tier structure, with specialized teams handling network and IP-related technical issues. Port forwarding is not available on consumer cellular service due to CGNAT; static IP allocations are not offered on the consumer mobile tier. Business wireless customers can request specific IP allocations through AT&T Business Mobility, though static cellular IPs are operationally rare compared to wireline allocations.

For abuse and reputation paths, AT&T maintainsabuse@att.netas the primary contact covering both wireline and wireless residential services, with separate enterprise paths for business customers. Mobile reputation issues are unusual to encounter because the CGNAT architecture means specific IP-level reputation is difficult to track at the subscriber level - any abuse attributed to an AT&T Mobility IP requires the carrier’s CGNAT mapping to identify the specific responsible subscriber rather than the public IP alone.

AT&T 5G deployment and the C-band spectrum strategy

AT&T’s 5G deployment strategy has centered on acquiring substantial C-band (3.7-3.98 GHz) spectrum through the FCC’s 2021 Auction 107, combined with existing low-band (700 MHz, 850 MHz) and high-band (39 GHz mmWave) holdings. The C-band buildout has proceeded gradually due to FAA-related deployment restrictions near airports that delayed full activation in some markets. Compared to T-Mobile’s 2.5 GHz dominance, AT&T’s mid-band 5G coverage is smaller but expanding, with throughput characteristics positioned between T-Mobile’s Ultra Capacity and traditional 4G LTE.

The spectrum mix affects IP-level behavior indirectly by determining what kind of performance a customer experiences on the AT&T Mobility network at any given location. A customer connected to C-band 5G sees throughput that approaches modest fiber speeds in good signal conditions; the same customer on low-band 5G or 4G LTE experiences markedly lower throughput ceilings. For investigations correlating AT&T Mobility traffic with bandwidth signatures, the underlying coverage tier matters substantially. Performance degradation that appears VPN-related on this network may reflect 5G coverage transitions rather than tunnel issues, especially in markets where C-band activation is uneven.

Quick reference summary for AT&T Mobility lookups

The high-confidence AT&T Mobility identification recipe is AS20057 plus CGNAT-style source-port distribution plus mobile-class geolocation. The ASN alone distinguishes wireless AT&T from wireline AT&T Internet reliably. Internet Air fixed- wireless customers share the same network identity as smartphone customers despite being marketed as residential broadband. Cricket Wireless and other AT&T prepaid brands ride on the same network and appear identical at the IP level. FirstNet produces a specialized public-safety traffic category that occasionally surfaces in lookups. Mature native IPv6 deployment makes the network effectively dual-stack with IPv6 as primary connectivity, producing significant leak surface for VPN clients that tunnel only IPv4. Specific subscriber attribution requires carrier-level CGNAT mapping through proper legal process. Treat AT&T Mobility attribution as a mobile-class signal in the broader AT&T family, layered with application or account-level evidence for consequential workflows.

For deeper context, pair this AT&T Mobility profile with the wireline AT&T Internet page when investigating "AT&T" attribution that could plausibly come from either side of the family. Same parent company, same Dallas headquarters, two fundamentally different network products at the IP level. The ASN distinction is the first signal to check, but understanding both networks’ profiles produces the most reliable AT&T-family interpretation across the wireless and wireline cases that the brand name does not separately distinguish for customers.

AT&T Mobility FAQ

What ASN does AT&T Mobility use?
AT&T Mobility may use one or multiple ASNs depending on region and service type. This page lists common references for quick investigation.
Can AT&T Mobility IP addresses change location results?
Yes. Geolocation can vary by database and routing design, especially on mobile or CGNAT-heavy networks.
How should I verify ISP ownership?
Cross-check ASN mapping with WHOIS/RDAP and reverse DNS to reduce false assumptions from one data source.
Is AT&T Mobility enough to identify an exact user location?
No. The ISP name is provider context. Exact location and subscriber-level identity require stronger evidence than public lookup data can provide.
Why do AT&T Mobility lookup results sometimes show nearby cities?
Provider aggregation, dynamic address pools, mobile gateways, and stale geolocation records can all make a correct ISP match appear under a nearby city.