Why does my ATT WiFi show connected but no internet access?

This typically means your device successfully joined the gateway's WiFi network and received a local IP address (192.168.1.x), but the gateway cannot route traffic to the internet. Common causes: (1) ATT's DNS servers are down — test by opening a site by IP like http://142.250.80.46 (Google). If that loads, it's a DNS issue; change your DNS to 1.1.1.1. (2) The gateway's PPPoE session with ATT's network dropped — perform a 30-second power cycle. (3) There is an ATT network outage in your area — check att.com/internet/outages.

Why is my ATT fiber internet slow all of a sudden even though nothing changed?

Sudden ATT fiber slow speeds without any configuration change usually point to: (1) Neighborhood congestion during peak hours (6–10 PM) on shared GPON segments — run a speed test at 2 AM to compare. (2) A background update or process on your device consuming bandwidth — check Task Manager or Activity Monitor. (3) WiFi channel interference from a newly installed neighbor device — log into http://192.168.1.254 and switch your 5 GHz channel manually. (4) ATT conducting maintenance on their backbone — check the ATT outage map. (5) Gateway thermal throttling — ensure the gateway has airflow and is not enclosed in a cabinet.

How do I restart my ATT router without losing my WiFi settings?

A standard restart (soft reboot) does NOT erase WiFi settings. You can restart safely via: (1) The ATT Smart Home Manager app — tap your gateway device and select Restart. (2) The gateway web UI at http://192.168.1.254 → Home Network → Restart → Restart Gateway. (3) Unplugging the power adapter for 30 seconds then plugging it back in. None of these methods reset your custom SSID, password, or port forwarding rules. Only pressing and holding the physical RESET pinhole button for 10 seconds performs a factory reset that erases all settings.

My ATT U-verse ethernet is not working but WiFi works fine — what's wrong?

If WiFi works but a wired Ethernet port does not, check: (1) The Ethernet cable — swap it with a known-good cable. Cat5e or better is required for gigabit. (2) The specific port on the gateway — try a different LAN port (BGW210 has 4 ports; some can fail independently). (3) The NIC on your computer — try the same cable on a different device. (4) Duplex mismatch — on Windows, open Device Manager → Network Adapters → your NIC → Properties → Advanced and set Speed & Duplex to 'Auto Negotiation'. (5) The gateway's switch chip — if all 4 LAN ports fail but WiFi works, the gateway needs replacement; contact ATT for an RMA.

Why is my ATT mobile hotspot not working even though I have LTE bars?

LTE signal bars indicate your phone is registered to the cell tower, but hotspot requires a separate data bearer and plan authorization. Check: (1) Your plan includes hotspot — log in to att.com/myatt or call 611. Many ATT prepaid and older legacy plans do not include hotspot. (2) You have not exceeded your monthly hotspot data cap — once exhausted, hotspot throttles to 128 kbps. (3) APN settings are correct: Settings → Cellular → Cellular Data Network → APN should be 'phone' (lowercase). (4) The hotspot feature is enabled on the account — if recently added, it can take up to 2 hours to provision. (5) Try toggling Airplane Mode to force re-registration to the data network.

ATT WiFi Not Working: Fix Slow, Disconnected & No Internet Issues (2024)

ATT WiFi not working or slow? Follow this step-by-step guide to fix ATT fiber slow speeds, lost connections, and 'connected but no internet' errors fast.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,666 words

Key Takeaways

Root Cause 1: Gateway/modem firmware freeze or memory leak causing ATT WiFi not working, slow speeds, or 'no broadband connection' errors — fixed by a proper restart sequence.
Root Cause 2: DNS misconfiguration or ISP-side outage causing 'ATT connected but no internet' — devices show WiFi signal but traffic cannot route to the internet.
Root Cause 3: Channel congestion, outdated WiFi band settings, or QoS misconfiguration causing ATT fiber slow WiFi and upload speed slow symptoms even when wired speeds are normal.
Root Cause 4: MTU mismatch or PPPoE session drop on ATT U-verse/Fiber causing ATT no broadband connection and ethernet not working errors.
Quick Fix Summary: Power-cycle gateway (30-second unplug), run a wired speed test to isolate WiFi vs. line issue, check att.com/outages for regional problems, then follow the step-by-step deep dive below.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle gateway (30-sec unplug)	First step for any ATT WiFi not working or slow issue	2 min	None
ATT Smart Home Manager app restart	Gateway reachable on local network, web UI inaccessible	3 min	None
Factory reset gateway (pinhole reset)	Persistent no broadband connection after all soft fixes	15 min	Erases custom WiFi/port settings
Change DNS to 8.8.8.8 / 1.1.1.1	ATT connected but no internet; pages time out despite signal	5 min	Low — reverts easily
Switch WiFi band (2.4 GHz ↔ 5 GHz)	ATT WiFi slow all of a sudden on one device only	2 min	None
Adjust MTU to 1492 (PPPoE)	ATT U-verse ethernet not working; large pages fail, small ones load	5 min	Low — test before committing
Update gateway firmware via att.com/myatt	ATT modem not working after recent ISP push; known firmware bugs	10 min	Low
Contact ATT support / schedule tech visit	Outdoor line damage, node outage, persistent ATT no network connection	30+ min	None on your end

Understanding ATT WiFi Not Working Errors

ATT residential internet — whether ATT Fiber (GPON/XGS-PON), ATT U-verse (VDSL2/IP-DSL), or ATT Fixed Wireless — all terminate at a gateway device (BGW320, BGW210, NVG599, or similar). When that gateway misbehaves, you may see any of the following symptoms:

Red or amber broadband light on the gateway front panel
'No Broadband Connection' in the gateway admin UI at http://192.168.1.254
'ATT connected but no internet' — devices associate to WiFi SSID, get a 192.168.1.x address, but DNS and HTTP traffic fail
ATT fiber slow download speed — wired Ethernet shows full speed but WiFi throughput is 10–50% of expected
ATT mobile hotspot not working — phone shows LTE/5G bars but data sessions fail or stall

Understanding which layer is broken (physical line → gateway WAN → gateway LAN → client WiFi) determines the correct fix path.

Step 1: Identify the Failure Layer

1a. Check the gateway indicator lights

Light	Color	Meaning
Broadband	Green	WAN link is up
Broadband	Red	No DSL/fiber sync
Broadband	Amber/Yellow	Syncing or authentication failed
Service	Green	Internet session active
Service	Red	Authenticated but no IP from ATT
WiFi	Green	Radio active
WiFi	Off	Radio disabled

If the Broadband light is red or amber, the problem is upstream of the gateway — either the physical cable/fiber drop or the ATT network node.

1b. Run a wired speed test

Plug a laptop directly into the gateway's LAN port with an Ethernet cable, then open https://speedtest.net or run the fast CLI (see Code Block section). If wired speeds are normal but WiFi is slow, the problem is isolated to the wireless radio or channel. If wired speeds are also slow or zero, the problem is the WAN connection.

1c. Check ATT outage status

Navigate to https://www.att.com/internet/speedtest/ and log in to check for reported outages in your area, or call 800-288-2020. ATT's network operations center posts active outages in the MyATT portal under Network Status.

Step 2: Fix WAN/Broadband Connection Issues

2a. Proper gateway restart sequence

A simple power button press sometimes does not fully flush PPPoE session state. The correct procedure:

Unplug the gateway's power adapter from the wall outlet.
Wait 30 full seconds (allows capacitors to discharge and session timers to expire on ATT's RADIUS server).
Plug power back in.
Wait 3–5 minutes for fiber/DSL sync and IP assignment before testing.

For ATT Fiber BGW320/BGW210, the ONT (white box near where the fiber enters your home) may also need to be restarted separately if the broadband light stays red after gateway restart.

2b. Restart via Smart Home Manager

If you can reach the gateway on the local network but the WAN is down, open http://192.168.1.254 in a browser, navigate to Home Network → Restart, and select Restart Gateway. This performs a clean session teardown.

2c. Fix 'No Broadband Connection' — PPPoE MTU issue

ATT U-verse uses PPPoE which encapsulates packets with an 8-byte overhead, so the effective MTU is 1492 instead of the standard 1500. If the gateway was reset or replaced without restoring this setting, large downloads succeed but HTTPS handshakes and large HTML pages fail (a classic "Black Hole" symptom).

On any Windows client, you can also force the correct MSS clamp:

netsh interface ipv4 set subinterface "Ethernet" mtu=1492 store=persistent

Step 3: Fix WiFi-Specific Slowness and Connection Failures

3a. ATT WiFi slow all of a sudden — channel congestion

The most common cause of sudden ATT WiFi slow performance in apartments or dense neighborhoods is overlapping 2.4 GHz channels. Log in to http://192.168.1.254 → Home Network → Wi-Fi → select your 2.4 GHz radio → change Channel from Auto to a fixed 1, 6, or 11 (the only non-overlapping 2.4 GHz channels in the US).

For ATT Fiber with a BGW320 supporting Wi-Fi 6 (802.11ax), prefer connecting devices to the 5 GHz or 6 GHz band. Verify band steering is enabled under Advanced → Wi-Fi → Band Steering.

3b. ATT connected but no internet — DNS resolution failure

ATT's default DNS servers (68.94.156.1 and 68.94.157.1) occasionally experience regional outages or return NXDOMAIN for valid domains (a known issue during ATT maintenance windows). To test:

nslookup google.com 8.8.8.8
nslookup google.com 68.94.156.1

If the first command succeeds and the second fails or times out, ATT's DNS is the problem. Override DNS on the gateway: http://192.168.1.254 → Settings → LAN → DHCP → set DNS1 to 1.1.1.1 and DNS2 to 8.8.8.8.

3c. ATT fiber slow WiFi despite good wired speeds

If wired Ethernet delivers full gigabit but WiFi tops out at 100–200 Mbps, investigate:

WiFi client capabilities: Many older devices are 802.11n (2-stream max ~300 Mbps theoretical). Use networksetup -getinfo Wi-Fi (macOS) or check Device Manager → Network Adapters (Windows) to confirm client spec.
Gateway placement: Move the gateway to a central location with no obstructions. Every wall reduces 5 GHz signal by ~6–12 dB.
WMM (WiFi Multimedia) QoS: Ensure WMM is enabled on the gateway. Disabling it can reduce 802.11n/ac throughput by up to 50%.
Transmit power: On BGW320/BGW210, verify transmit power is set to High under Advanced → Wi-Fi.

3d. ATT hotspot not working / ATT cell service slow

For mobile hotspot issues, first confirm your ATT data plan includes hotspot (not all prepaid plans do). Then:

Toggle Airplane Mode on and off to force a new LTE/5G registration.
Reset network settings: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings (iOS) or Settings → General Management → Reset → Reset Network Settings (Android).
Verify APN settings: ATT LTE APN should be phone with no special auth.
If on a SIM that was recently ported or reactivated, allow up to 4 hours for full provisioning.

Step 4: Advanced — Factory Reset and Line Tests

4a. Factory reset gateway

Use this only after all other steps fail. Insert a paperclip into the pinhole RESET button on the back of the gateway, hold for 10 seconds until lights flash, then release. The gateway will reboot to factory defaults. You will need your WiFi credentials (printed on the gateway label) to reconnect.

4b. ATT line/fiber diagnostics

Log in to http://192.168.1.254 → Diagnostics → Troubleshoot & Resolve → run the built-in line test. For fiber, check the ONT (Optical Network Terminal) status light; a red or off PON light means the fiber drop or ATT-side equipment needs a technician.

For U-verse DSL, check line stats at http://192.168.1.254 → Broadband → DSL Status: look for SNR Margin (should be >6 dB; lower = line noise problem) and Attenuation (higher = longer line, lower max speed). These numbers are definitive evidence to present to ATT support when requesting a line tech visit.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ATT Internet Diagnostic Script
# Works on macOS and Linux; for Windows use PowerShell equivalents below
# Run with: bash att_diag.sh

echo "============================================"
echo " ATT Internet Diagnostic Tool"
echo "============================================"

# 1. Check default gateway (should be 192.168.1.254 for ATT)
echo ""
echo "[1] Default Gateway:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  GATEWAY=$(netstat -nr | awk '/default/ {print $2; exit}')
else
  GATEWAY=$(ip route | awk '/default/ {print $3; exit}')
fi
echo "    Gateway IP: $GATEWAY"

# 2. Ping the gateway (LAN connectivity test)
echo ""
echo "[2] Pinging ATT Gateway ($GATEWAY):"
ping -c 4 $GATEWAY 2>/dev/null | tail -3

# 3. Ping ATT DNS servers
echo ""
echo "[3] Pinging ATT DNS servers:"
ping -c 3 68.94.156.1 2>/dev/null | tail -2
ping -c 3 68.94.157.1 2>/dev/null | tail -2

# 4. DNS resolution test — ATT DNS vs Google DNS
echo ""
echo "[4] DNS Resolution Test:"
echo "    ATT DNS (68.94.156.1):"
nslookup google.com 68.94.156.1 2>/dev/null | grep -E 'Address|SERVFAIL|timed out'
echo "    Google DNS (8.8.8.8):"
nslookup google.com 8.8.8.8 2>/dev/null | grep -E 'Address|SERVFAIL|timed out'

# 5. HTTP connectivity test by IP (bypasses DNS)
echo ""
echo "[5] HTTP Test by IP (bypasses DNS — tests pure routing):"
curl -s -o /dev/null -w "    HTTP Status: %{http_code}  Connect Time: %{time_connect}s  Total Time: %{time_total}s\n" http://142.250.80.46 --connect-timeout 5

# 6. Traceroute to ATT's first hop
echo ""
echo "[6] Traceroute (first 8 hops):"
if command -v traceroute &> /dev/null; then
  traceroute -m 8 -n 8.8.8.8 2>/dev/null
else
  tracepath -n -m 8 8.8.8.8 2>/dev/null
fi

# 7. MTU path discovery (detects PPPoE MTU mismatch)
echo ""
echo "[7] MTU Path Discovery Test (1492 bytes = ATT PPPoE standard):"
ping -c 2 -M do -s 1464 8.8.8.8 2>/dev/null && echo "    MTU 1492: OK" || echo "    MTU 1492: FAILED — possible MTU mismatch, set gateway MTU to 1492"
ping -c 2 -M do -s 1472 8.8.8.8 2>/dev/null && echo "    MTU 1500: OK (non-PPPoE or MTU already correct)" || echo "    MTU 1500: FAILED (expected on PPPoE lines)"

# 8. Speed test using curl (rough bandwidth estimate)
echo ""
echo "[8] Download Speed Estimate (100MB test file from fast.com CDN):"
DURATION=10
URL="http://speedtest.tele2.net/100MB.zip"
curl -o /dev/null --max-time $DURATION -w "    Downloaded: %{size_download} bytes in ${DURATION}s\n    Avg Speed: %{speed_download} bytes/sec\n" $URL 2>/dev/null

# 9. WiFi signal info (macOS)
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo ""
  echo "[9] WiFi Signal Info (macOS):"
  /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I 2>/dev/null | grep -E 'SSID|RSSI|channel|lastTxRate|MCS|PHY'
fi

# 10. WiFi signal info (Linux)
if command -v iwconfig &> /dev/null; then
  echo ""
  echo "[9] WiFi Signal Info (Linux):"
  iwconfig 2>/dev/null | grep -E 'ESSID|Signal|Bit Rate|Frequency'
fi

echo ""
echo "============================================"
echo " Diagnostic Complete"
echo " If wired ping to $GATEWAY fails: hardware/cable issue"
echo " If DNS fails but IP ping works: change DNS to 1.1.1.1"
echo " If all pings fail: power-cycle gateway 30 sec"
echo " ATT support: 800-288-2020 | att.com/internet/outages"
echo "============================================"

# --- Windows PowerShell equivalents ---
# Test-NetConnection -ComputerName 192.168.1.254
# Test-NetConnection -ComputerName 8.8.8.8 -Port 53
# Resolve-DnsName google.com -Server 68.94.156.1
# Resolve-DnsName google.com -Server 8.8.8.8
# Test-Connection -ComputerName 8.8.8.8 -BufferSize 1464
# netsh interface ipv4 show subinterfaces
# netsh interface ipv4 set subinterface "Ethernet" mtu=1492 store=persistent
# Get-NetAdapter | Format-Table Name, Status, LinkSpeed

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing ISP connectivity issues, home network infrastructure, and cloud-edge networking. Our troubleshooting guides are tested on live hardware before publication and updated quarterly to reflect firmware changes and ISP network topology updates.

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.