Why is my ATT WiFi connected but showing no internet?

This classic 'connected but no internet' state usually means your device successfully joined the WiFi network but the gateway itself lost its connection to ATT's network. The most common causes are: (1) a stale PPPoE session that needs a 60-second power cycle to clear, (2) an ATT outage in your area, or (3) the gateway failed to obtain a valid WAN IP address. Check the Broadband LED on your gateway — if it's red or flashing, the problem is on ATT's side of the line. Power cycle, check the outage map, and if the WAN IP is 0.0.0.0 in your gateway settings, contact ATT.

Why did my ATT WiFi become slow all of a sudden?

Sudden ATT WiFi slowdowns are typically caused by: (1) Network congestion during peak hours (7–10 PM), (2) a new device consuming bandwidth (check http://192.168.1.254 > Home Network > Devices), (3) WiFi interference from neighboring networks on the same channel — use a WiFi analyzer app and switch your gateway to a less congested channel, or (4) ATT performing network maintenance. Run a speed test at fast.com and compare to your plan speed. If wired speeds are normal but WiFi is slow, the issue is radio interference or band steering.

How do I properly restart my ATT router/gateway?

The correct ATT restart procedure is: Unplug the power cord from the back of the gateway (do not just press the power button). Wait 60 full seconds — this is critical to clear all session caches. If you have a fiber ONT box (usually a white box near where the fiber enters your home), unplug that too and wait the same 60 seconds. Plug in the ONT first and wait for its sync light to turn solid green. Then plug in the gateway and wait 3–5 minutes. Alternatively, use the ATT Smart Home Manager app > My Home > Network > Restart, but the physical unplug method is more thorough.

Why is my ATT Fiber download speed slow even though I'm paying for 1Gbps?

ATT Fiber customers commonly see below-expected speeds due to: (1) WiFi bottleneck — WiFi6 (802.11ax) is required to approach 1Gbps wirelessly; test with a wired Ethernet connection first, (2) MTU mismatch — set MTU to 1492 for PPPoE connections, (3) old Ethernet cable — you need Cat6 or better for gigabit speeds, (4) the speed test server itself being congested — test on multiple servers at speedtest.net and fast.com, (5) using the 2.4GHz band instead of 5GHz. Use a direct Ethernet connection to the BGW320/BGW210 gateway port and run a speed test — if you get near 1Gbps there, the issue is your home WiFi network, not ATT's line.

My ATT mobile hotspot is not working — how do I fix it?

ATT mobile hotspot failures have several common causes: (1) Your plan may not include hotspot — log into att.com/myatt to verify your features, (2) You've exhausted your hotspot data allotment (ATT throttles to 128Kbps after the limit), (3) APN settings are corrupt — go to Settings > Cellular > Cellular Data Options > Reset APN Settings, (4) The device needs a carrier settings update — on iPhone check Settings > General > About, (5) Try toggling Airplane Mode on for 30 seconds then off to force a fresh network registration. If the hotspot shows 'Personal Hotspot: 0 of 0 devices connected' and no devices can see it, restart the phone completely.

ATT WiFi Not Working: Complete Fix Guide for Slow, Connected But No Internet & Connection Failures

ATT WiFi not working or slow? Follow our step-by-step guide to fix ATT internet issues, restart your router, and restore full speed in minutes.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,447 words

Key Takeaways

Root Cause 1: Router or gateway firmware glitch causing 'connected but no internet' — fixed by a proper power cycle or factory reset.
Root Cause 2: Network congestion, outdated DNS settings, or ISP-side outage causing ATT WiFi slow or no broadband connection errors.
Root Cause 3: Incorrect MTU, duplex mismatch, or faulty splitter on ATT Fiber/U-verse lines causing slow download/upload speeds.
Quick Fix Summary: Power cycle your ATT gateway (unplug 60 sec), run a diagnostic ping and traceroute, update DNS to 8.8.8.8, and check ATT outage map before calling support.

ATT WiFi Fix Approaches Compared
Method	When to Use	Time	Risk
Power Cycle Gateway	ATT WiFi not connecting, connected but no internet, modem not working	2–5 min	None
Restart via ATT Smart Home Manager App	ATT wifi problems, att wifi slow all of a sudden, quick remote reboot needed	1–2 min	None
DNS Server Change (8.8.8.8 / 1.1.1.1)	ATT slow internet, att wifi slow, att internet speed slow	3 min	Low
MTU Adjustment (1492 for PPPoE)	ATT fiber slow download speed, att upload speed slow, packet loss detected	5 min	Low
Factory Reset Gateway	ATT no broadband connection, att no network connection, all else fails	15–20 min	High — erases settings
Check & Replace Ethernet/Coax Cables	ATT U-verse ethernet not working, att modem not working, intermittent drops	10 min	None
Contact ATT Support / Schedule Technician	ATT outage confirmed, att fiber slow despite all fixes, line degradation	1–3 days	None

Understanding ATT WiFi & Internet Failures

ATT internet issues range from complete outages ("ATT no broadband connection") to frustrating slowdowns ("ATT fiber slow wifi", "ATT internet very slow"). The symptoms often look identical — your device shows "Connected" with a WiFi icon, but pages won't load and you see errors like:

"No Internet, Secured" (Windows)
"Connected to WiFi but no internet" (Android/iOS)
"ATT Broadband Connection Lost" on the gateway LCD
"DNS_PROBE_FINISHED_NO_INTERNET" in Chrome
"ERR_NETWORK_CHANGED" on repeated page refreshes

These errors share a small set of root causes. This guide walks through each systematically.

Step 1: Determine the Scope of the Problem

Before touching hardware, determine whether the issue is local or upstream.

Check the ATT outage map: Visit https://www.att.com/internet/network-outage/ or text "OUTAGE" to 611611. If there is a confirmed outage in your area, no local fix will help — wait for ATT to resolve it.

Isolate the device:

Can another device connect? If yes, the problem is device-specific, not ATT's network.
Is every device affected? The issue is with the gateway, modem, or ATT line.

Check the ATT gateway status lights:

Solid Green (Broadband LED): Line is up. Problem is downstream (router, WiFi, device).
Flashing Red (Broadband LED): No DSL/Fiber signal. Line or splitter problem.
Solid Red: Authentication failure (PPPoE credentials rejected).
Amber/Yellow: Firmware update in progress — wait 10 minutes.

Step 2: Power Cycle Your ATT Gateway (Correct Method)

A standard "reboot" from the app is not always sufficient. Use this procedure:

Unplug the power cord from your ATT gateway (BGW320, BGW210, NVG599, etc.).
If you have a separate ONT (Optical Network Terminal) for fiber, unplug it too.
Wait 60 full seconds — this clears all session state, ARP tables, and DHCP leases.
Plug in the ONT first (if applicable), wait for it to sync (solid green light, ~30 sec).
Plug in the gateway. Wait up to 3 minutes for full initialization.
Test connectivity.

Why this works: ATT gateways cache stale PPPoE session IDs and DHCP bindings. A 60-second cold boot forces re-authentication with ATT's BRAS (Broadband Remote Access Server).

Step 3: Run Network Diagnostics from Your Computer

Use the commands in the Code Block section below to run a full diagnostic sweep. Key things to check:

Ping the gateway: If ping 192.168.1.254 (default ATT gateway IP) fails, the issue is between your device and the router (bad cable, bad WiFi association, IP conflict).

Ping ATT's DNS: If ping 68.94.156.1 (ATT's primary DNS) fails but the gateway responds, the problem is between your gateway and ATT's network — a line issue or outage.

Ping 8.8.8.8 (Google DNS): If this fails, ATT's upstream routing is down. If this succeeds but ping google.com fails, you have a DNS resolution problem only.

Run a traceroute: If packets drop at hops 2–3 (inside ATT's network), it confirms an ISP-side issue. If packets drop at hop 1 (your gateway), the problem is local.

Step 4: Fix ATT WiFi Slow / ATT Internet Speed Slow Issues

4a. Change Your DNS Servers

ATT's default DNS servers (68.94.156.1 and 68.94.157.1) can become congested or slow. Switch to faster resolvers:

Google DNS: 8.8.8.8 and 8.8.4.4
Cloudflare DNS: 1.1.1.1 and 1.0.0.1

On Windows: netsh interface ip set dns "Wi-Fi" static 1.1.1.1 then netsh interface ip add dns "Wi-Fi" 1.0.0.1 index=2

On the gateway itself: Log into http://192.168.1.254 > Settings > LAN > DHCP, and set the DNS fields there so all devices benefit automatically.

4b. Fix ATT Fiber Slow Download Speed — MTU Adjustment

ATT Fiber uses PPPoE, which has a maximum MTU of 1492 (not the standard 1500). Mismatches cause packet fragmentation, leading to slow speeds and partial page loads.

Check your current MTU: netsh interface ipv4 show subinterfaces (Windows)

If it shows 1500, update it: netsh interface ipv4 set subinterface "Ethernet" mtu=1492 store=persistent

Alternatively, set it in your gateway: Login > Settings > Broadband > PPPoE > MTU = 1492.

4c. Fix ATT WiFi Slow — 2.4GHz vs. 5GHz Band Steering

ATT gateways broadcast both 2.4 GHz and 5 GHz under the same SSID. Older or distant devices may lock onto 2.4 GHz. Log into http://192.168.1.254 > Settings > Wi-Fi and separate the bands into two distinct SSIDs (e.g., ATT-Home-2G and ATT-Home-5G). Connect performance-sensitive devices to 5 GHz.

4d. ATT U-verse Ethernet Not Working — Check for Duplex Mismatch

For wired connections, duplex mismatch causes severe slowdowns or complete failure. Run: netsh interface show interface — look for "Connection State: Disconnected" or errors.

Then force 1Gbps Full Duplex in Device Manager > Network Adapter > Properties > Advanced.

4e. ATT Mobile Hotspot Not Working

For ATT mobile hotspot failures:

Toggle Airplane Mode off/on to force a new LTE/5G cell registration.
Verify your ATT data plan includes hotspot — some base plans exclude it.
Reset APN settings: Settings > General > Transfer or Reset iPhone > Reset Network Settings (iOS) or Settings > General Management > Reset > Reset Network Settings (Android).
Check your data usage — ATT throttles hotspot speeds after plan limits are exceeded.

Step 5: Factory Reset as Last Resort

If all else fails and the gateway shows "No Broadband Connection" consistently:

Locate the Reset pinhole on the back of the gateway.
Press and hold with a paperclip for 10–15 seconds until the LED flashes.
Wait 5 minutes for the device to fully reinitialize.
Reconfigure your WiFi name and password.
If still failing after reset, the gateway hardware is faulty — contact ATT for a replacement.

Warning: Factory reset erases all custom settings including port forwarding rules, static IP assignments, and custom DNS configurations.

Step 6: When to Call ATT Support

Escalate to ATT (800-288-2020) if:

Outage map confirms service disruption in your area.
Broadband LED stays red after factory reset and power cycle.
Speeds are consistently below 50% of your subscribed plan after all fixes.
Technician diagnostics show high attenuation or signal loss on the fiber/DSL line.
Your ATT modem shows error code "IP Passthrough Failed" or "RG Reboot Loop".

Frequently Asked Questions

bash

#!/bin/bash
# ============================================================
# ATT WiFi & Internet Diagnostic Script
# Works on Linux/macOS. For Windows, see inline PowerShell cmds.
# ============================================================

ATT_GATEWAY="192.168.1.254"
ATT_DNS="68.94.156.1"
GOOGLE_DNS="8.8.8.8"
CLOUDFLARE_DNS="1.1.1.1"
ATT_DOMAIN="att.com"

echo "====== ATT Network Diagnostic ======"
echo "Timestamp: $(date)"
echo ""

# --- Step 1: Check local IP configuration ---
echo "[1] Local Network Configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ipconfig getifaddr en0 2>/dev/null && echo "WiFi IP (en0): $(ipconfig getifaddr en0)"
  ipconfig getifaddr en1 2>/dev/null && echo "Ethernet IP (en1): $(ipconfig getifaddr en1)"
  networksetup -getinfo Wi-Fi | grep -E 'IP address|Subnet mask|Router'
else
  ip addr show | grep -E 'inet ' | awk '{print $2}'
  ip route show default
fi
echo ""

# --- Step 2: Ping the ATT gateway ---
echo "[2] Pinging ATT Gateway ($ATT_GATEWAY):"
ping -c 4 -W 2 $ATT_GATEWAY
GATEWAY_STATUS=$?
if [ $GATEWAY_STATUS -ne 0 ]; then
  echo "ERROR: Cannot reach gateway. Check Ethernet cable or WiFi association."
fi
echo ""

# --- Step 3: Ping ATT DNS ---
echo "[3] Pinging ATT DNS ($ATT_DNS):"
ping -c 4 -W 2 $ATT_DNS
ATT_DNS_STATUS=$?
if [ $ATT_DNS_STATUS -ne 0 ]; then
  echo "WARNING: ATT DNS unreachable. ISP-side issue or outage likely."
fi
echo ""

# --- Step 4: Ping Google DNS (bypass ATT DNS) ---
echo "[4] Pinging Google DNS ($GOOGLE_DNS):"
ping -c 4 -W 2 $GOOGLE_DNS
GOOGLE_STATUS=$?
if [ $GOOGLE_STATUS -eq 0 ] && [ $ATT_DNS_STATUS -ne 0 ]; then
  echo "DIAGNOSIS: ATT DNS is down but internet works. Switch DNS to 8.8.8.8"
fi
echo ""

# --- Step 5: DNS resolution test ---
echo "[5] DNS Resolution Test for att.com:"
nslookup $ATT_DOMAIN $GOOGLE_DNS
echo ""

# --- Step 6: Traceroute to diagnose where packets drop ---
echo "[6] Traceroute to Google DNS (shows where routing fails):"
traceroute -m 20 -w 2 $GOOGLE_DNS 2>/dev/null || traceroute6 $GOOGLE_DNS 2>/dev/null
echo ""

# --- Step 7: MTU check (ATT Fiber PPPoE = 1492) ---
echo "[7] Current MTU Values:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  networksetup -getMTU Wi-Fi
  networksetup -getMTU Ethernet
else
  ip link show | grep mtu
fi
echo "NOTE: ATT Fiber PPPoE connections should use MTU=1492"
echo ""

# --- Step 8: Check for packet loss on sustained ping ---
echo "[8] Packet Loss Test (20 pings to 8.8.8.8):"
ping -c 20 -i 0.5 $GOOGLE_DNS | tail -2
echo ""

# --- Step 9: Speed test via curl (rough bandwidth check) ---
echo "[9] Download Speed Estimate (10MB test file):"
curl -o /dev/null --max-time 15 -w "Speed: %{speed_download} bytes/sec\nTime: %{time_total}s\n" \
  "https://speed.cloudflare.com/__down?bytes=10000000" 2>/dev/null
echo ""

echo "====== Diagnostic Complete ======"
echo "If gateway unreachable: Power cycle (unplug 60 sec)"
echo "If DNS fails only: Run: sudo networksetup -setdnsservers Wi-Fi 1.1.1.1 8.8.8.8 (macOS)"
echo "Check ATT outage map: https://www.att.com/internet/network-outage/"
echo ""

# ============================================================
# WINDOWS POWERSHELL EQUIVALENTS (run in PowerShell as Admin)
# ============================================================
# Test-NetConnection -ComputerName 192.168.1.254
# Test-NetConnection -ComputerName 8.8.8.8 -Port 53
# Resolve-DnsName att.com -Server 1.1.1.1
# tracert 8.8.8.8
# netsh interface ipv4 show subinterfaces
# netsh interface ipv4 set subinterface "Wi-Fi" mtu=1492 store=persistent
# netsh interface ip set dns "Wi-Fi" static 1.1.1.1
# netsh interface ip add dns "Wi-Fi" 1.0.0.1 index=2
# ipconfig /flushdns
# ipconfig /release && ipconfig /renew
# netsh winsock reset
# Restart-NetAdapter -Name "Wi-Fi"

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps and SRE engineers with 10+ years of experience diagnosing ISP connectivity issues, home network infrastructure, and enterprise networking. Our guides are based on hands-on troubleshooting experience with ATT Fiber, U-verse, and mobile networks, cross-referenced with official ATT support documentation and community-verified fixes.

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.