Why does my Xfinity WiFi say 'connected but no internet'?

This classic symptom means your device successfully associated with the gateway and received an IP address (Layer 2/3 are working), but the gateway itself cannot reach Xfinity's upstream network. The most common causes are: (1) an active Xfinity outage — check statuspage.xfinity.com; (2) a failed modem registration — the modem obtained a private IP from the CMTS but never received a public WAN IP (power-cycle fixes this 80% of the time); (3) a DNS failure — the modem has internet connectivity but DNS resolution is broken; try pinging 8.8.8.8 directly. If the ping to 8.8.8.8 works but websites don't load, change your DNS server to 8.8.8.8 or 1.1.1.1 in your OS network settings.

My Xfinity network is not showing up on any device — what happened?

If the SSID completely disappeared, the most likely causes are: (1) the WiFi radio was accidentally disabled — log in to http://10.0.0.1 and re-enable 2.4 GHz and 5 GHz under Gateway → WiFi; (2) the SSID was set to 'Hidden' — toggle this off in the same admin panel; (3) a firmware update rebooted the gateway into a state where the radio failed to initialize — power-cycle and wait 3 minutes; (4) hardware failure of the WiFi radio module — factory reset first, and if the SSID still doesn't appear, request a gateway replacement from Xfinity.

Why is my Xfinity internet slower than my plan?

Speed below plan tier is usually caused by one of: (1) WiFi interference or weak signal — always test over ethernet first; if wired speed matches the plan, the problem is your WiFi environment; (2) an undersized modem — DOCSIS 3.0 16-channel modems cannot deliver Gigabit speeds; upgrade to a DOCSIS 3.1 device; (3) node congestion — if wired speeds are also low and mtr shows high latency at Xfinity's first hop, your local node is congested, typically during peak hours (7–11 PM); report it to Xfinity as a sustained performance issue; (4) xFi Advanced Security or parental controls throttling traffic — temporarily disable in the Xfinity app to test.

My Xfinity modem won't turn on or has no lights — how do I fix it?

If the modem has no LED activity: (1) confirm the power adapter is fully seated in both the modem and the wall outlet — try a different outlet to rule out a tripped circuit; (2) check that the outlet is live by plugging in another device; (3) inspect the power adapter for damage; Xfinity XB gateways use a 12V DC adapter — a failed adapter is common; (4) if the modem is warm or smells burnt, it has failed internally and needs replacement — contact Xfinity to exchange it at an xFinity store or arrange a shipment; (5) if you recently had a power surge, the internal fuse or circuitry may be blown — a surge protector or UPS is recommended for future prevention.

I can't connect to Xfinity WiFi even though the network shows up — password is correct but it won't connect.

When the network is visible but the device won't authenticate: (1) 'forget' the network on your device and reconnect fresh — stale credentials or a corrupted network profile is the most common cause; (2) confirm you are entering the password from the gateway label (case-sensitive); (3) check if MAC address filtering is enabled in the gateway admin portal — add your device's MAC address to the allow list; (4) if the gateway shows the error 'authentication timeout,' the 5 GHz radio may be overloaded — connect explicitly to the 2.4 GHz SSID (usually labeled with a '-2G' suffix) as a workaround; (5) on Android, disable 'Private/Random MAC' for the Xfinity network — randomized MACs can conflict with gateway DHCP reservations.

Xfinity WiFi Not Working, Not Showing Up, or Connected But No Internet: Complete Troubleshooting Guide

Fix Xfinity WiFi issues fast: no connection, modem not turning on, slow speeds, or network not showing up. Step-by-step guide with real commands.

Last updated: February 27, 2026

Last verified: February 27, 2026

3,017 words

Key Takeaways

Root cause 1: Modem/gateway hardware failure or power issue — the device may be stuck in a boot loop, unresponsive, or physically damaged, causing Xfinity modems to not turn on or not respond to commands.
Root cause 2: ISP-side outage or provisioning failure — Xfinity's backend may have an active outage, an expired DHCP lease, or a failed modem registration that prevents the device from obtaining a public IP, resulting in 'connected but no internet' symptoms.
Root cause 3: WiFi radio or SSID configuration problem — the gateway's 2.4 GHz or 5 GHz radio may be disabled, the SSID may be hidden, or band-steering may be malfunctioning, causing the Xfinity network to not show up on client devices.
Quick fix summary: Power-cycle the modem/gateway (unplug 60 seconds), check the Xfinity Status Center for outages, factory-reset the gateway if configuration is corrupt, update firmware via the Xfinity app, and run the diagnostic commands below to isolate whether the problem is on your LAN, the gateway, or upstream with Xfinity's network.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem/gateway	First step for any Xfinity connectivity issue — modem not responding, WiFi stopped working, no connection	2–5 min	None
Xfinity Status Center / My Account app outage check	Suspect ISP-side outage; 'connected but no internet' after modem boots cleanly	1–2 min	None
Release/renew DHCP lease from gateway admin UI	Device shows 'connected, no internet'; gateway has IP but clients don't	3–5 min	Low — brief disconnect
Factory reset Xfinity gateway (WPS/reset button)	Persistent WiFi not showing up, SSID missing, corrupt config after firmware update	10–15 min	Medium — wipes custom settings
Re-provision modem via Xfinity app or 1-800-XFINITY	Modem not connecting to internet after hardware swap or account change	10–20 min	Low
Replace coax/ethernet splitter or cable	Intermittent drops, slow speed, modem won't sync downstream channels	15–30 min	Low
Upgrade modem firmware via Xfinity admin portal	Xfinity internet lagging, speed slower than plan, known firmware bugs	5–10 min	Low — brief reboot
Swap gateway hardware (RMA or xFi Pod)	Modem won't turn on, hardware fault confirmed, all other steps failed	1–2 days	None once replaced

Understanding Xfinity WiFi Issues

Xfinity (Comcast) delivers internet over a hybrid fiber-coaxial (HFC) network. Your Xfinity gateway (e.g., XB6, XB7, XB8) or a third-party cable modem bridged to a router sits at the edge of your home network. When any layer in this chain fails — from the coax line to the CMTS at Xfinity's headend — you can see symptoms ranging from "Xfinity WiFi not showing up" to "connected but no internet" to speeds far below your plan.

The five distinct failure domains are:

Power/Hardware — modem won't turn on, no LED activity
Physical Layer — bad coax, damaged splitter, poor signal levels
ISP Provisioning — DHCP failure, CMTS registration timeout, outage
Gateway Configuration — WiFi radio disabled, SSID hidden, firewall rule blocking traffic
Client Device — incorrect saved credentials, IP conflict, corrupted network profile

Step 1: Identify the Symptom Precisely

Before touching hardware, match your symptom to the correct failure domain:

Symptom	Likely Domain
No LED lights on modem	Power / Hardware
US/DS light blinking indefinitely	Physical Layer / ISP
Online light solid, WiFi SSID missing	Gateway Config / Radio
WiFi visible, password fails	Client credentials
WiFi connects, browser shows "no internet"	ISP Provisioning / DNS
Speed 50%+ below plan	Physical Layer / Congestion

Step 2: Check for an Active Xfinity Outage

Always rule out an ISP-side outage first. Visit statuspage.xfinity.com or open the Xfinity app → Account → Internet → View Status. You can also text "OUTAGE" to 266278 (COMCAST) for a status update.

If an outage is confirmed, there is nothing to fix locally — wait for restoration and monitor Xfinity's status feed.

Step 3: Power-Cycle the Modem/Gateway

This resolves the majority of cases including "Xfinity modem not responding," "WiFi stopped working," and "connected but no internet."

Unplug the power cable from the back of the Xfinity gateway or modem.
If you use a separate router, unplug it as well.
Wait a full 60 seconds — this clears the DRAM-cached DHCP state and forces a fresh CMTS registration.
Plug the modem back in first and wait for the Online or 2.4G/5G LED to become solid (up to 3 minutes).
Plug the router back in.
On your computer or phone, disconnect from the WiFi network and reconnect.

Step 4: Inspect Physical Connections

Loose or corroded coax is a silent killer of cable internet performance.

Hand-tighten the coax F-connector at the back of the modem and at the wall plate.
Remove any coax splitter in the direct modem run — each splitter adds 3.5 dB of signal loss.
Look for visible damage: kinks, sharp bends, or water ingress in the connector.
If you have a spare coax patch cable, swap it.

Step 5: Access the Modem Signal Levels Page

Open a browser and navigate to http://10.0.0.1 (Xfinity XB gateways) or http://192.168.100.1 (third-party modems). Go to Connected Devices → Downstream/Upstream or the Signal tab.

Healthy cable modem signal thresholds (DOCSIS 3.0/3.1):

Downstream power: -7 dBmV to +7 dBmV
Downstream SNR: ≥ 33 dB (QAM256), ≥ 30 dB (QAM64)
Upstream power: 38–48 dBmV

If values are outside these ranges, the issue is physical (coax, splitter, or line amplifier) or requires an Xfinity technician to correct the signal at the tap/node.

Step 6: Diagnose with Command-Line Tools

Use the commands in the code_block section below to quickly determine whether the problem is your LAN, the gateway, or upstream DNS/routing.

Key decision points from the diagnostics:

If ping 10.0.0.1 (or your gateway IP) fails → gateway is unreachable or has crashed → power-cycle or factory reset.
If gateway pings but ping 8.8.8.8 fails → ISP upstream issue or modem not provisioned → call Xfinity or re-provision.
If ping 8.8.8.8 succeeds but ping google.com fails → DNS resolution broken → change DNS to 8.8.8.8 or 1.1.1.1 in your network adapter settings.
If all pings succeed but speed is low → run traceroute to identify latency hops, or check for WiFi interference.

Step 7: Fix WiFi Not Showing Up (SSID Missing)

If the Xfinity network is not visible on any device:

Log in to the gateway admin portal at http://10.0.0.1 (credentials on the gateway label).
Navigate to Gateway → Connection → WiFi.
Confirm 2.4 GHz and 5 GHz radios are both Enabled.
Verify the SSID is not set to Hidden/Closed.
Check that Band Steering is not causing all clients to be pushed to 5 GHz (which some older devices can't see).
Save settings and wait 60 seconds for the radios to restart.

Alternatively, use the Xfinity app → WiFi → Edit WiFi Settings to toggle radio bands without logging into the admin UI.

Step 8: Factory Reset as a Last Resort

If WiFi is still not working after all above steps, a configuration corruption may have occurred (common after firmware updates).

Locate the Reset pinhole button on the back of the gateway.
With the unit powered on, hold the reset button for 30 seconds using a paperclip.
All LEDs will flash; release the button.
The gateway will reboot to factory defaults (~3–5 minutes).
Reconnect using the default SSID and password printed on the gateway label.
Re-provision via the Xfinity app if required.

Warning: This erases all custom SSIDs, passwords, port-forwarding rules, and parental controls.

Step 9: Addressing Speed Issues (Slower Than Plan)

If you're connected but Xfinity internet is slower than usual or not getting full speed:

Run a wired speed test first (speedtest-cli --server-id <nearest>) to rule out WiFi as the bottleneck.
Check that your modem supports enough downstream channels for your plan tier (e.g., a DOCSIS 3.0 modem with 16 channels maxes out at ~600 Mbps; Gigabit requires DOCSIS 3.1 or 32+ channel 3.0).
Confirm you are not on a throttled or congested node — run mtr --report 8.8.8.8 to see per-hop latency; consistent high latency at the first external hop (Xfinity's CMTS) indicates node congestion.
Disable QoS or xFi Advanced Security temporarily in the Xfinity app to see if it is artificially limiting throughput.
If using eero with Xfinity, ensure the Xfinity gateway is in Bridge Mode to avoid double-NAT, which can cap speeds and cause eero Xfinity issues.

Step 10: eero + Xfinity Specific Issues

Users pairing eero mesh routers with Xfinity gateways frequently encounter double-NAT and IP conflicts.

In the Xfinity gateway admin portal, go to Gateway → At a Glance and enable Bridge Mode.
Connect eero's WAN port to a LAN port on the Xfinity gateway.
Factory-reset eero and set it up fresh via the eero app.
Confirm eero receives a public IP (not 192.168.x.x or 10.x.x.x) on its WAN interface — this confirms bridge mode is active.

Note: Enabling bridge mode disables the Xfinity gateway's own WiFi. You will manage all WiFi through eero.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Xfinity Connectivity Diagnostic Script
# Compatible with macOS and Linux (WSL2 on Windows)
# Run: bash xfinity_diag.sh
# ============================================================

GATEWAY_IP="10.0.0.1"          # Default Xfinity XB gateway
ALT_GATEWAY="192.168.100.1"    # Third-party modem admin page
DNS_TEST="8.8.8.8"             # Google DNS — bypass local DNS to test routing
DNS_HOSTNAME="google.com"      # Hostname for DNS resolution test

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

# --- 1. Show current network interface configuration ---
echo "[1] Network Interface Info:"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |state '
else
  ifconfig | grep -E 'inet |status'
fi
echo ""

# --- 2. Show routing table (confirm default gateway) ---
echo "[2] Routing Table:"
if command -v ip &>/dev/null; then
  ip route show
else
  netstat -rn
fi
echo ""

# --- 3. Detect actual gateway IP dynamically ---
ACTUAL_GW=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' | head -1)
if [ -z "$ACTUAL_GW" ]; then
  ACTUAL_GW=$(netstat -rn 2>/dev/null | awk '/^0\.0\.0\.0|^default/ {print $2}' | head -1)
fi
echo "[3] Detected Default Gateway: ${ACTUAL_GW:-NOT FOUND}"
echo ""

# --- 4. Ping the gateway ---
echo "[4] Ping Gateway (${ACTUAL_GW:-$GATEWAY_IP}) — tests LAN connectivity:"
ping -c 4 -W 2 "${ACTUAL_GW:-$GATEWAY_IP}" 2>&1
echo ""

# --- 5. Ping Xfinity gateway admin page IPs ---
echo "[5] Ping Xfinity Admin Page ($GATEWAY_IP):"
ping -c 2 -W 2 "$GATEWAY_IP" 2>&1
echo ""

# --- 6. Ping external IP (bypasses DNS, tests ISP routing) ---
echo "[6] Ping External IP ($DNS_TEST) — tests ISP upstream routing:"
ping -c 4 -W 3 "$DNS_TEST" 2>&1
if [ $? -ne 0 ]; then
  echo "RESULT: Cannot reach external IP. Likely ISP outage or modem not provisioned."
else
  echo "RESULT: External IP reachable. ISP routing is UP."
fi
echo ""

# --- 7. Test DNS resolution ---
echo "[7] DNS Resolution Test ($DNS_HOSTNAME via system DNS):"
if command -v nslookup &>/dev/null; then
  nslookup "$DNS_HOSTNAME" 2>&1
elif command -v dig &>/dev/null; then
  dig +short "$DNS_HOSTNAME" 2>&1
fi
echo ""

# --- 8. Test DNS with Google's server directly ---
echo "[8] DNS via Google 8.8.8.8 (bypass local DNS):"
if command -v nslookup &>/dev/null; then
  nslookup "$DNS_HOSTNAME" 8.8.8.8 2>&1
elif command -v dig &>/dev/null; then
  dig +short "$DNS_HOSTNAME" @8.8.8.8 2>&1
fi
echo ""

# --- 9. Traceroute to first 5 hops (identify where latency/drops occur) ---
echo "[9] Traceroute to 8.8.8.8 (first 8 hops — find latency spike):"
if command -v mtr &>/dev/null; then
  mtr --report --report-cycles 5 --max-ttl 8 8.8.8.8 2>&1
elif command -v traceroute &>/dev/null; then
  traceroute -m 8 -w 2 8.8.8.8 2>&1
else
  echo "Install mtr (brew install mtr / apt install mtr) for best results."
fi
echo ""

# --- 10. Speed test via CLI (requires speedtest-cli: pip install speedtest-cli) ---
echo "[10] Speed Test (wired connection recommended for accurate results):"
if command -v speedtest-cli &>/dev/null; then
  speedtest-cli --simple 2>&1
elif command -v speedtest &>/dev/null; then
  speedtest 2>&1
else
  echo "Install speedtest-cli: pip install speedtest-cli or brew install speedtest-cli"
  echo "Then re-run this section or visit fast.com / speedtest.net in a browser."
fi
echo ""

# --- 11. Check WiFi signal strength (Linux only) ---
echo "[11] WiFi Signal Strength:"
if command -v iwconfig &>/dev/null; then
  iwconfig 2>&1 | grep -E 'ESSID|Signal|Bit Rate|Link'
elif command -v nmcli &>/dev/null; then
  nmcli dev wifi list 2>&1 | head -20
else
  echo "On macOS: Hold Option and click WiFi icon to see RSSI and noise floor."
fi
echo ""

# --- 12. Flush DNS cache and renew DHCP (Linux) ---
echo "[12] Flush DNS Cache:"
if command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches && echo "systemd-resolved DNS cache flushed."
elif [ -f /etc/init.d/nscd ]; then
  sudo /etc/init.d/nscd restart && echo "nscd restarted."
else
  echo "On macOS run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder"
  echo "On Windows run: ipconfig /flushdns"
fi
echo ""

# --- 13. Release and renew DHCP lease ---
echo "[13] Renew DHCP Lease (gets fresh IP from gateway):"
ACTIVE_IFACE=$(ip route show default 2>/dev/null | awk '/default/ {print $5}' | head -1)
if [ -n "$ACTIVE_IFACE" ]; then
  echo "Active interface: $ACTIVE_IFACE"
  if command -v dhclient &>/dev/null; then
    sudo dhclient -r "$ACTIVE_IFACE" && sudo dhclient "$ACTIVE_IFACE" && echo "DHCP lease renewed on $ACTIVE_IFACE."
  else
    echo "dhclient not found. On macOS: sudo ipconfig set $ACTIVE_IFACE DHCP"
    echo "On Windows: ipconfig /release && ipconfig /renew"
  fi
else
  echo "Could not auto-detect active interface. Run manually: sudo dhclient -r eth0 && sudo dhclient eth0"
fi
echo ""

echo "===== Diagnostic Complete ====="
echo "If external ping (step 6) fails: power-cycle modem, check Xfinity outage status."
echo "If DNS fails (step 7) but external ping works: set DNS to 8.8.8.8 or 1.1.1.1."
echo "If all passes but speed is low: test wired, check modem signal levels at http://10.0.0.1"

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing ISP connectivity issues, home network architectures, and cable modem infrastructure. We write practical, command-line-verified troubleshooting guides tested on real hardware.

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.