Why does my AT&T WiFi show connected but have no internet access?

This happens when your device successfully connects to the AT&T gateway's local network (WiFi association succeeds) but the gateway itself cannot reach AT&T's backbone. The most common causes are: (1) the gateway's WAN DHCP lease expired and wasn't renewed, (2) AT&T's authentication server rejected the gateway's credentials after a firmware update, or (3) a regional AT&T outage. Start by power-cycling the gateway for 60 seconds, then check whether the 'Service' or 'Broadband' light on the gateway is red or off — that confirms the WAN link is down and the issue is upstream of your home network.

My AT&T internet was working fine, then suddenly stopped. No settings changed — what happened?

Sudden drops with no configuration changes are almost always one of three things: an AT&T infrastructure outage (check downdetector.com/status/att), a gateway firmware update that installed in the background and caused a reboot loop, or a DHCP lease expiration that the gateway failed to renew. Power-cycle the gateway first. If the 'Service' light returns to solid green within 5 minutes, the issue resolved itself (likely a brief outage). If it stays red or orange, call AT&T at 1-800-288-2020 for a line test.

How do I fix 'ATT connected to WiFi but no internet' on my phone specifically?

When only your phone shows no internet while other devices work, the issue is device-specific. Try these steps in order: (1) Toggle WiFi off and on to force a new DHCP lease. (2) Forget the AT&T network and reconnect. (3) On Android go to Settings → Network & Internet → WiFi → [your network] → forget, then reconnect. On iPhone go to Settings → WiFi → tap the (i) next to your network → Forget This Network, then reconnect. (4) If you still see a '!' warning icon next to the WiFi signal, go to your phone's WiFi settings and set DNS manually to 8.8.8.8. (5) As a last resort, reset network settings on the phone (Settings → General → Transfer or Reset → Reset → Reset Network Settings on iOS).

How long does an AT&T internet outage typically last?

Minor AT&T outages caused by equipment resets or routing changes typically resolve in 15–60 minutes. Outages caused by fiber cuts or major infrastructure failures can last 4–24 hours depending on the location and severity. AT&T's SLA for residential service does not guarantee restoration time, but AT&T Business customers with an SLA agreement can escalate to priority support. You can check real-time restoration estimates at att.com → Support → Outage Information, or through the AT&T Smart Home Manager app.

Will factory resetting my AT&T BGW320 gateway fix the no internet problem?

A factory reset fixes no-internet issues caused by corrupted gateway configuration, a stuck firmware state, or a misconfigured DMZ/firewall rule that blocks outbound traffic. However, it will NOT fix issues caused by AT&T outages, failed ONT hardware, or degraded DSL/fiber signals — those require AT&T technician intervention. Before factory resetting, try a power cycle (unplug 60 seconds) and an IP renewal on your devices. Only proceed with a factory reset if the gateway's admin page at http://192.168.1.254 is unreachable or shows persistent errors after multiple reboots.

ATT No Internet Connection: How to Fix 'Connected to WiFi But No Internet' on AT&T

Fix AT&T no internet connection errors fast. Step-by-step guide covering gateway resets, DNS fixes, IP renewal, and AT&T outage checks. Restore access in minute

Last updated: February 27, 2026

Last verified: February 27, 2026

2,576 words

Key Takeaways

Root cause 1: AT&T gateway or modem firmware freeze — the device shows lights as normal but fails to route traffic, requiring a power cycle or factory reset.
Root cause 2: DHCP lease failure or IP address conflict — your device receives an APIPA address (169.254.x.x) instead of a valid gateway IP, blocking all outbound traffic.
Root cause 3: DNS resolution failure — AT&T's default DNS servers become unreachable or return NXDOMAIN for all queries, making sites appear down even though the physical connection is live.
Root cause 4: AT&T regional outage or provisioning issue — the fiber or DSL line is authenticated but the backbone route is severed, confirmed via AT&T's outage map.
Quick fix summary: Power-cycle the gateway (unplug 60 seconds), release/renew IP on your device, switch DNS to 8.8.8.8 or 1.1.1.1, and check AT&T's outage portal at downdetector.com or att.com/internet/outage.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle AT&T gateway	Gateway lights normal but no internet traffic passes	2–5 min	Low — no settings lost
IP release and renew (ipconfig/dhclient)	Device shows 169.254.x.x or 0.0.0.0 IP address	1–2 min	Low — reconnects automatically
Flush DNS cache and change DNS servers	Sites fail to load but ping to IP addresses works	2–3 min	Low — reversible anytime
Factory reset AT&T BGW320 / BGW210 gateway	Multiple reboots failed, admin page unreachable	10–15 min	Medium — all custom settings erased
Check AT&T outage map and contact support	Entire neighborhood offline, no fix works locally	Varies	None — informational only
Re-run AT&T Smart Home Manager provisioning	New install or after gateway replacement	5–10 min	Low — guided wizard
Disable IPv6 on gateway or client	IPv4 works but IPv6 traffic drops; mixed connectivity	3–5 min	Low — can be re-enabled

Understanding the AT&T No Internet Connection Error

When AT&T customers report 'no internet connection' the symptom can manifest in several distinct ways depending on where in the network stack the failure occurs. You might see Windows display 'Connected, no internet' in the system tray, macOS showing an exclamation mark on the WiFi icon, or a browser returning ERR_INTERNET_DISCONNECTED or DNS_PROBE_FINISHED_NO_INTERNET. On mobile devices the status bar may read 'WiFi — No Internet'. Understanding which layer is broken is the first step to choosing the right fix.

AT&T residential service typically uses one of three gateway models: the BGW320-500 (fiber), BGW210-700 (fiber/DSL combo), or older NVG589/NVG599 units. Each can fail in subtly different ways but the diagnostic process is the same.

Step 1: Identify the Failure Layer

Check your device's assigned IP address first.

If your IP starts with 169.254.x.x, your device never received a valid DHCP lease from the gateway. This points to a DHCP server failure on the gateway or a blocked DHCP broadcast.

If your IP is a valid RFC-1918 address (192.168.x.x or 10.0.x.x) but you still have no internet, the gateway itself has lost its upstream WAN connection or DNS is broken.

Ping the gateway:

ping 192.168.1.254

(Default AT&T gateway IP. Yours may differ — check your device's default gateway in network settings.)

If the ping fails → the local link between your device and the gateway is broken (WiFi association issue, bad cable, or gateway crash).
If the ping succeeds → the local network is fine; the problem is upstream.

Ping a public IP directly:

ping 8.8.8.8

If this fails → the AT&T gateway cannot route traffic to the internet (WAN-side outage, PPPoE/DHCP failure on the modem, or AT&T provisioning issue).
If this succeeds but websites still don't load → DNS is broken.

Test DNS resolution:

nslookup google.com
nslookup google.com 8.8.8.8

If the first command returns a timeout or SERVFAIL but the second returns a valid IP, AT&T's DNS servers are the culprit.

Step 2: Fix Layer 1 — Power-Cycle the AT&T Gateway

This resolves the majority of AT&T no-internet reports. Gateway firmware can enter an unstable state after prolonged uptime, a brief power fluctuation, or a failed background firmware update.

Unplug the gateway's power cord from the wall outlet (do not press the reset button yet).
If you have a separate ONT (Optical Network Terminal — the white box mounted on the wall) also unplug it.
Wait 60 full seconds — this clears capacitor charge and forces a full memory flush.
Plug the ONT back in first and wait for its status light to turn solid green (up to 2 minutes).
Plug the gateway back in and wait for the Broadband and Service lights to turn solid green. This can take 3–5 minutes on fiber.
Reconnect your devices and retest.

BGW320 light reference:

Power: Solid green = OK
Broadband: Solid green = WAN link up
Service: Solid green = Internet authenticated
Service: Flashing green = Attempting to authenticate (wait)
Service: Red = Authentication failed (AT&T account/provisioning issue)

Step 3: Fix Layer 2 — Release and Renew Your IP Address

If the gateway is healthy but your device has an APIPA address, force a new DHCP lease.

Windows:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

macOS:

sudo ipconfig set en0 DHCP
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

(Replace en0 with your active interface — use networksetup -listallnetworkservices to find it.)

Linux:

sudo dhclient -r eth0
sudo dhclient eth0

If your device still won't get a DHCP lease after renewal, try connecting via ethernet cable directly to the gateway to rule out a WiFi-specific issue. Also check whether other devices on the same network have valid IPs — if they do, the problem is isolated to your device's network stack.

Step 4: Fix Layer 3 — Resolve DNS Failures

At&T uses 68.94.156.1 and 68.94.157.1 as its default DNS resolvers. These occasionally become unreachable during congestion events or maintenance.

Windows — change DNS via PowerShell:

Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("8.8.8.8","1.1.1.1")
ipconfig /flushdns

macOS — change DNS via terminal:

networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1
dscacheutil -flushcache

Linux — edit /etc/resolv.conf:

sudo nano /etc/resolv.conf
# Replace or add:
nameserver 8.8.8.8
nameserver 1.1.1.1

After changing DNS, test immediately:

nslookup google.com
curl -I https://google.com

Step 5: Factory Reset the AT&T Gateway (Last Resort)

If all software fixes fail and AT&T confirms no outage in your area, a factory reset may clear corrupted firmware state.

BGW320 / BGW210 reset procedure:

With the gateway powered on, locate the recessed Reset button on the back panel.
Use a paperclip to press and hold for 10 seconds until the power light blinks red.
Release and wait 5 minutes for the full reboot cycle.
Reconnect using the credentials printed on the gateway label.
Re-run AT&T Smart Home Manager setup at http://192.168.1.254.

Warning: A factory reset removes all custom WiFi names, passwords, port forwarding rules, and static IP assignments. Document your settings before proceeding.

Step 6: Check for AT&T Outages

If nothing above works, the issue is likely infrastructure-level:

Visit att.com → Support → Check for Outages and enter your address.
Check downdetector.com/status/att for real-time crowd-sourced reports.
Call AT&T support at 1-800-288-2020 and request a line test — technicians can see signal levels on your ONT or DSL line remotely.
In the AT&T Smart Home Manager app, tap Network → Troubleshoot for automated diagnostics.

Advanced: Checking Gateway Logs

For technically advanced users, the AT&T gateway exposes a diagnostic log at http://192.168.1.254/cgi-bin/broadbandstatistics.ha (BGW320) or similar paths. Look for:

PPPoE timeout messages → authentication failures
DHCP NAK entries → upstream ISP rejecting your gateway's lease request
DNS SERVFAIL logs → internal DNS proxy issues

These logs can pinpoint whether the problem is authentication-based (requires AT&T account verification) or signal-based (requires physical repair).

Frequently Asked Questions

bash

#!/usr/bin/env bash
# AT&T No Internet Connection — Diagnostic & Fix Script
# Run on Linux/macOS. Windows users: use the ipconfig commands in comments.
# Usage: chmod +x att_diag.sh && sudo ./att_diag.sh

GATEWAY="192.168.1.254"   # Default AT&T gateway IP
PUBLIC_IP="8.8.8.8"       # Google DNS — tests WAN routing
DNS_TEST="google.com"     # Domain for DNS resolution test

echo "======================================="
echo " AT&T Internet Connection Diagnostics"
echo "======================================="

# --- Step 1: Show current IP and gateway ---
echo ""
echo "[1] Current network configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  IFACE=$(route get default 2>/dev/null | awk '/interface:/{print $2}')
  ipconfig getifaddr "$IFACE" 2>/dev/null && echo "Interface: $IFACE"
  netstat -rn | grep default | head -3
else
  ip addr show | grep 'inet ' | grep -v '127.0.0.1'
  ip route show default
fi
# Windows equivalent:
# ipconfig /all | findstr /i "IPv4 Gateway DNS"

# --- Step 2: Check for APIPA address (169.254.x.x) ---
echo ""
echo "[2] Checking for APIPA address (169.254.x.x = DHCP failure):"
if ip addr show 2>/dev/null | grep -q '169.254'; then
  echo "WARNING: APIPA address detected — DHCP lease failed!"
  echo "Fix: Renewing DHCP lease..."
  IFACE=$(ip route | awk '/default/{print $5}' | head -1)
  sudo dhclient -r "$IFACE" 2>/dev/null
  sudo dhclient "$IFACE" 2>/dev/null
  echo "DHCP renewal attempted on $IFACE"
else
  echo "OK: No APIPA address detected."
fi
# Windows equivalent:
# ipconfig /release && ipconfig /renew

# --- Step 3: Ping the local gateway ---
echo ""
echo "[3] Pinging AT&T gateway at $GATEWAY:"
if ping -c 3 -W 2 "$GATEWAY" &>/dev/null; then
  echo "OK: Gateway is reachable (local network is healthy)."
else
  echo "FAIL: Cannot reach gateway at $GATEWAY"
  echo "Action: Check WiFi/ethernet connection or power-cycle gateway."
fi
# Windows equivalent:
# ping 192.168.1.254

# --- Step 4: Ping public IP (bypass DNS) ---
echo ""
echo "[4] Pinging public IP $PUBLIC_IP (tests WAN routing, bypasses DNS):"
if ping -c 3 -W 3 "$PUBLIC_IP" &>/dev/null; then
  echo "OK: WAN routing is working. If websites fail, DNS is the issue."
else
  echo "FAIL: Cannot reach $PUBLIC_IP"
  echo "Action: AT&T WAN connection is down. Power-cycle gateway."
  echo "        If still failing, check att.com for outages."
fi
# Windows equivalent:
# ping 8.8.8.8

# --- Step 5: Test DNS resolution ---
echo ""
echo "[5] Testing DNS resolution for $DNS_TEST:"
AT&T_DNS_RESULT=$(nslookup "$DNS_TEST" 68.94.156.1 2>&1 | grep -i 'address' | tail -1)
GOOGLE_DNS_RESULT=$(nslookup "$DNS_TEST" 8.8.8.8 2>&1 | grep -i 'address' | tail -1)

if [ -z "$AT&T_DNS_RESULT" ]; then
  echo "FAIL: AT&T DNS (68.94.156.1) did not resolve $DNS_TEST"
  echo "Action: Switching to Google DNS..."
else
  echo "OK: AT&T DNS resolved $DNS_TEST -> $AT&T_DNS_RESULT"
fi

if [ -z "$GOOGLE_DNS_RESULT" ]; then
  echo "FAIL: Google DNS (8.8.8.8) also failed — WAN is down, not just DNS."
else
  echo "OK: Google DNS resolved $DNS_TEST -> $GOOGLE_DNS_RESULT"
  if [ -z "$AT&T_DNS_RESULT" ]; then
    echo "FIX APPLIED: Setting DNS to 8.8.8.8 and 1.1.1.1..."
    if [[ "$OSTYPE" == "darwin"* ]]; then
      networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1
      dscacheutil -flushcache && sudo killall -HUP mDNSResponder
    else
      echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf
      echo "nameserver 1.1.1.1" | sudo tee -a /etc/resolv.conf
    fi
    echo "DNS updated. Retest with: nslookup google.com"
  fi
fi
# Windows equivalent:
# nslookup google.com 68.94.156.1
# nslookup google.com 8.8.8.8
# netsh interface ip set dns "Wi-Fi" static 8.8.8.8

# --- Step 6: HTTP connectivity test ---
echo ""
echo "[6] HTTP connectivity test:"
HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://www.google.com)
if [ "$HTTP_CODE" == "200" ] || [ "$HTTP_CODE" == "301" ] || [ "$HTTP_CODE" == "302" ]; then
  echo "OK: HTTPS to google.com returned HTTP $HTTP_CODE — internet is working!"
else
  echo "FAIL: HTTPS request returned code '$HTTP_CODE' or timed out."
  echo "Action: If DNS and ping to 8.8.8.8 both work, check firewall rules."
fi

# --- Step 7: Check AT&T outage (informational) ---
echo ""
echo "[7] AT&T outage check links:"
echo "  -> https://www.att.com/internet/outage/"
echo "  -> https://downdetector.com/status/att/"
echo "  -> Run 'traceroute 8.8.8.8' to see where packets drop."

echo ""
echo "======================================="
echo " Diagnostics complete."
echo "======================================="

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, network administrators, and SRE practitioners with 10+ years of combined experience troubleshooting ISP connectivity issues, home network configurations, and enterprise infrastructure. Our guides are based on hands-on testing with real hardware and verified against official vendor documentation. We specialize in translating cryptic error messages into actionable, step-by-step fixes for both technical and non-technical users.

Sources

Explore More wifi Guides

"Connected Without Internet" Error: Complete Fix Guide for Wi-Fi, Routers, Android & ISP Issues

Fix the "Connected Without Internet" error on Wi-Fi, Android, hotspots & routers. Step-by-step commands for Cox, CenturyLink, Frontier, T-Mobile & more.

"Connected Without Internet" Error: Complete Fix Guide for WiFi, Routers, Android & ISP Issues

Fix the 'connected without internet' error on WiFi, Android, hotspots & ISPs like Cox, CenturyLink & Fios. Step-by-step commands and solutions inside.

"Connected Without Internet" Error: What It Means and How to Fix It (All Devices & ISPs)

Fix the 'Connected Without Internet' WiFi error on Android, router, hotspot, Cox, CenturyLink, Fios & more. Step-by-step commands and solutions inside.