Error Medic

Troubleshooting Verizon Router: Fix 'Connected Without Internet', Slow Speeds & No Internet Issues

Fix Verizon router issues: connected but no internet, slow WiFi, 5G slower than 4G, ONT failures. Step-by-step commands and reboot sequences included.

Last updated:
Last verified:
2,607 words
Key Takeaways
  • Root cause 1: ONT (Optical Network Terminal) lease failure or fiber signal loss causes 'connected without internet' even when WiFi shows full bars — fix by power-cycling the ONT and router in the correct sequence.
  • Root cause 2: Verizon 5G Home Internet may fall back to slower 4G LTE bands or experience congestion on mmWave frequencies, making 5G appear slower than 4G — fix by repositioning the gateway or forcing band steering in the admin console.
  • Root cause 3: DHCP lease exhaustion, DNS misconfiguration, or corrupted ARP cache on the router causes the 'internet connected but no internet' symptom — fix by releasing/renewing DHCP, flushing DNS, and resetting the router to factory defaults if needed.
  • Quick fix summary: (1) Power-cycle ONT → router → device in sequence, (2) check Verizon outage map, (3) run ipconfig/ip commands to verify DHCP lease, (4) swap DNS to 8.8.8.8, (5) factory reset as last resort.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Power-cycle ONT + Router (correct sequence)First step for any 'no internet' or 'connected without internet' symptom5–10 minNone — safe to do anytime
Release/Renew DHCP lease on client deviceDevice shows 169.254.x.x or wrong subnet IP2 minTemporary network drop during renewal
Flush DNS cache on client deviceSites load for some domains but not others; DNS resolution errors1 minNone
Change DNS servers on router (e.g., 8.8.8.8)All devices on network can't resolve hostnames despite IP connectivity5 minLow — revert easily if worse
Force 5G band / reposition 5G gatewayVerizon 5G slower than 4G, intermittent drops10–30 minLow — may temporarily worsen signal during repositioning
Reset router to factory defaultsAll other steps fail; persistent misconfiguration20 minMedium — loses all custom settings
Contact Verizon support / dispatch technicianONT light codes indicate fiber signal loss, upstream hardware fault1–3 daysNone for user; requires Verizon access

Understanding Verizon Router & Internet Issues

Verizon FiOS and Verizon 5G Home Internet use fundamentally different last-mile technologies, but they share many of the same failure modes at the router and gateway layer. Understanding which infrastructure you're on is the first diagnostic step.

FiOS (Fiber): Uses an Optical Network Terminal (ONT) mounted inside or outside your home. The ONT converts fiber-optic signal to Ethernet or coax, which feeds your Verizon-provided router (typically a G3100 or CR1000A). If the ONT loses its optical signal or fails to authenticate with Verizon's BRAS (Broadband Remote Access Server), your router will show a valid LAN connection but the WAN interface will have no IP — producing the dreaded 'connected without internet' state.

5G Home Internet: Uses a dedicated gateway (e.g., ASK-NCQ1338FA or Nokia FastMile) that acts as both modem and router. It connects to Verizon's 5G NR (mmWave or Sub-6 GHz) or 4G LTE network. When mmWave signal is marginal, the gateway silently falls back to LTE, which can actually deliver better throughput than a weak mmWave connection — causing the confusing 'Verizon 5G slower than 4G' symptom.


Step 1: Verify the Scope of the Problem

Before touching any hardware, determine whether this is a Verizon network outage, an ONT/gateway failure, or a local router/device issue.

  1. Check Verizon's outage map: Visit https://www.verizon.com/home/outage/ or use the My Verizon app. If there's a confirmed outage in your area, hardware troubleshooting won't help — wait it out.
  2. Check router WAN status: Log into your router admin console at http://192.168.1.1 (FiOS routers) or http://192.168.0.1 (5G gateways). Navigate to My Network → Network Connections → Broadband Connection. If the WAN IP is 0.0.0.0 or blank, the router has no upstream IP.
  3. Check ONT status lights (FiOS only): The ONT has indicator LEDs:
    • PON light solid green: Fiber signal is good.
    • PON light blinking or red: Fiber signal lost — call Verizon.
    • Data/Ethernet light off: ONT is not passing traffic to router.

Step 2: Power-Cycle ONT and Router in the Correct Sequence

Random reboots often fail because users restart in the wrong order. The ONT must fully boot and authenticate before the router requests a DHCP lease from Verizon's network.

Correct sequence:

  1. Unplug the router's power cord.
  2. Unplug the ONT's power cord (or remove its battery backup if present).
  3. Wait 60 full seconds.
  4. Plug in the ONT first. Wait for PON and Ethernet lights to go solid green (~90 seconds).
  5. Plug in the router. Wait 3–5 minutes for full boot and WAN IP assignment.
  6. Test connectivity from a wired client before testing WiFi.

For 5G Home Internet: Unplug the gateway, wait 60 seconds, plug back in. The gateway renegotiates 5G/LTE registration during boot.


Step 3: Diagnose Client-Side IP and DNS

If the router has a valid WAN IP but individual devices show 'connected without internet', the problem is likely DHCP, DNS, or a client-side routing issue.

Run the diagnostic commands in the code_block section below to check your IP address, default gateway, DNS servers, and actual internet reachability.

What to look for:

  • If your device IP starts with 169.254.x.x, it received an APIPA address — DHCP failed. Restart your network adapter or power-cycle the router.
  • If you can ping 8.8.8.8 (IP) but not ping google.com (hostname), DNS is broken. Change your DNS.
  • If you can't ping 8.8.8.8 from the device but the router admin shows a valid WAN IP, check your device's firewall or try a wired connection.
  • If traceroute stalls at the first hop (192.168.1.1), the router's WAN is down despite showing connected.

Step 4: Fix DNS Issues

Verizon's DNS servers sometimes experience degraded performance or partial outages. Switch to Google or Cloudflare DNS:

  • Google DNS: 8.8.8.8 / 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 / 1.0.0.1

Change DNS on the router (not just the device) so all connected clients benefit:

  1. Log into router admin at http://192.168.1.1.
  2. Navigate to My Network → Network Connections → Broadband Connection → Settings.
  3. Uncheck 'Obtain DNS Server Address Automatically'.
  4. Enter 8.8.8.8 and 8.8.4.4.
  5. Save and reboot the router.

Step 5: Troubleshoot Verizon 5G Slower Than 4G

This is one of the most counter-intuitive Verizon problems. mmWave 5G (the ultra-fast variety) has extremely limited range and is blocked by walls, windows, and rain. Sub-6 GHz 5G has better range but isn't dramatically faster than LTE in practice.

Diagnosis:

  1. Log into the 5G gateway admin console.
  2. Look for the Signal Strength / Band indicator. Note the RSRP (Reference Signal Received Power) and RSRQ values.
    • RSRP better than -85 dBm: Good 5G signal.
    • RSRP between -85 and -105 dBm: Marginal, likely falling back to LTE.
    • RSRP worse than -105 dBm: Poor signal — 4G LTE will outperform.
  3. Run a speed test at https://fast.com and note whether it's labeled 5G or LTE.

Fixes for slow 5G:

  • Reposition the gateway: Place it near a window facing the direction of the nearest Verizon 5G tower. Even a 2-foot move can dramatically improve mmWave RSRP.
  • Use the Verizon 5G Home app: It includes a signal strength visualizer to find the optimal placement spot.
  • Elevate the gateway: Higher placement (on a shelf or window sill) reduces obstructions.
  • Avoid interference: Keep the gateway away from microwaves, cordless phones, and metal surfaces.

Step 6: Factory Reset as Last Resort

If all else fails and the router has a valid WAN IP but behavior is still erratic, a corrupted routing table, NAT table overflow, or firmware bug may be to blame.

FiOS G3100 factory reset:

  • Press and hold the reset button on the back of the router for 10 seconds until lights flash.
  • The router will reboot to factory defaults. You'll need to reconfigure WiFi SSID, password, and any custom settings.

Warning: After factory reset, FiOS routers re-register with Verizon's provisioning server automatically. However, if your router was manually registered (common after self-install), you may need to call Verizon at 1-800-VERIZON to re-provision.


Step 7: Escalate to Verizon Support

Escalate immediately if:

  • PON light on ONT is red or blinking.
  • You see Event ID errors in the router log referencing PPPoE authentication failed or DHCP WAN timeout.
  • The router admin shows WAN IP: 0.0.0.0 after multiple reboots.
  • Speed tests from a wired connection to the router show <10 Mbps on a plan rated for 300+ Mbps.

Request a line test and ask Verizon to check the optical power level at the ONT. Acceptable optical receive power is typically between -8 dBm and -27 dBm. Outside this range indicates a fiber plant issue requiring a technician dispatch.

Frequently Asked Questions

bash
#!/usr/bin/env bash
# ============================================================
# Verizon Router Diagnostic Script
# Compatible with: macOS, Linux (adapt ipconfig commands for Windows)
# Run as: bash verizon_diag.sh
# ============================================================

echo "======================================="
echo " Verizon Router Diagnostic Tool"
echo "======================================="
echo ""

# --- 1. Show current IP configuration ---
echo "[1] Current IP Configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  # macOS
  ifconfig | grep -E 'inet |status:'
else
  # Linux
  ip addr show | grep -E 'inet |state '
fi
echo ""

# --- 2. Check default gateway ---
echo "[2] Default Gateway:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  netstat -rn | grep 'default'
else
  ip route | grep default
fi
echo ""

# --- 3. Ping gateway (Verizon router LAN IP) ---
GATEWAY="192.168.1.1"  # Change to 192.168.0.1 for 5G Home Internet gateway
echo "[3] Pinging Verizon Router/Gateway at $GATEWAY:"
ping -c 4 $GATEWAY
echo ""

# --- 4. Ping Verizon's DNS server ---
echo "[4] Pinging Verizon DNS (4.2.2.1):"
ping -c 4 4.2.2.1
echo ""

# --- 5. Ping Google DNS by IP (tests WAN routing, no DNS needed) ---
echo "[5] Pinging Google DNS 8.8.8.8 by IP (WAN routing test):"
ping -c 4 8.8.8.8
echo ""

# --- 6. DNS resolution test ---
echo "[6] DNS Resolution Test (google.com):"
nslookup google.com 2>&1 || dig google.com
echo ""

# --- 7. Traceroute to detect where traffic stops ---
echo "[7] Traceroute to 8.8.8.8 (first 10 hops):"
if [[ "$OSTYPE" == "darwin"* ]]; then
  traceroute -m 10 8.8.8.8
else
  traceroute -m 10 8.8.8.8 2>/dev/null || tracepath -m 10 8.8.8.8
fi
echo ""

# --- 8. Check MTU (oversized MTU causes partial connectivity) ---
echo "[8] MTU Test (ping with large packet to 8.8.8.8):"
ping -c 2 -s 1472 -M do 8.8.8.8 2>&1 || echo "MTU may be too large - consider setting router MTU to 1492 (PPPoE) or 1500 (DHCP)"
echo ""

# --- 9. Flush DNS cache ---
echo "[9] Flushing local DNS cache:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed."
else
  sudo systemd-resolve --flush-caches 2>/dev/null && echo "systemd DNS cache flushed." \
  || sudo /etc/init.d/nscd restart 2>/dev/null && echo "nscd restarted."
fi
echo ""

# --- 10. Release and renew DHCP (Linux only) ---
if [[ "$OSTYPE" != "darwin"* ]]; then
  IFACE=$(ip route | grep default | awk '{print $5}' | head -1)
  echo "[10] Releasing and renewing DHCP on interface $IFACE:"
  sudo dhclient -r $IFACE && sleep 2 && sudo dhclient $IFACE
  echo "DHCP renewed. New IP:"
  ip addr show $IFACE | grep 'inet '
fi

# --- Windows equivalents (run in PowerShell or CMD) ---
# ipconfig /all                          # Show IP config
# ping 192.168.1.1                       # Ping router
# ping 8.8.8.8                          # Ping by IP (no DNS)
# tracert 8.8.8.8                        # Traceroute
# nslookup google.com 8.8.8.8           # DNS test against Google
# ipconfig /release && ipconfig /renew  # Renew DHCP
# ipconfig /flushdns                    # Flush DNS cache
# netsh winsock reset                   # Reset Winsock (last resort)
# netsh int ip reset                    # Reset TCP/IP stack

echo "======================================="
echo " Diagnostic Complete"
echo " If WAN ping (step 5) fails but"
echo " gateway ping (step 3) succeeds,"
echo " the issue is between your router"
echo " and Verizon's network (ONT/WAN)."
echo "======================================="
E

Error Medic Editorial

Error Medic's editorial team consists of senior DevOps engineers, SREs, and network administrators with 10+ years of experience troubleshooting ISP-level connectivity issues, enterprise routing, and consumer networking hardware. Our guides are tested against real hardware and validated against official vendor documentation before publication.

Sources

Related Articles in Verizon

Explore More wifi Guides