Why does my Verizon FiOS say 'connected' but there's no internet?

This almost always means your router has a valid local network connection but has failed to obtain a WAN IP address from Verizon's DHCP servers, or the ONT upstream has lost its fiber signal. Check the ONT PON light (should be solid green), then log into your router at 192.168.1.1 and verify the Broadband Connection shows a valid public IP (not 0.0.0.0 or 169.254.x.x). Power-cycle the ONT first, wait 5 minutes, then reboot the router. If the problem persists, release and renew the DHCP lease from the router admin panel.

Why is Verizon 5G slower than 4G LTE on my phone?

Verizon's Nationwide 5G uses Dynamic Spectrum Sharing (DSS) which shares spectrum with LTE, often resulting in speeds equal to or slower than pure LTE. Ultra Wideband (mmWave) 5G is fast only within ~300 feet of a compatible tower with line of sight. If your phone shows '5G' but you're far from a UWB node, it's connecting via Sub-6 DSS which can underperform LTE. Temporarily force LTE in your phone's network settings to compare speeds. If LTE is consistently faster, report the 5G coverage issue to Verizon via the My Verizon app.

How do I troubleshoot the Verizon ONT when there is no internet?

Start by inspecting the ONT's indicator lights: the PON light must be solid green for fiber connectivity, and the WAN light should be solid green to confirm the Ethernet link to your router. If PON is solid red, the fiber signal is lost — inspect the fiber cable for sharp bends or a disconnected SC/APC connector at the junction box. Unplug the ONT power for 60 seconds and reconnect. If the PON light does not return to solid green within 10 minutes, contact Verizon support — a field technician is required to restore the optical signal.

My Verizon internet is extremely slow — what are the most common causes?

Common causes of Verizon slow internet include: (1) Wi-Fi interference from neighboring networks — use a Wi-Fi analyzer app to find a less congested channel and switch the router to 5 GHz or 6 GHz; (2) Router QoS or bandwidth throttling — check the router admin panel for active QoS rules; (3) Outdated router firmware — update via the My Fios app or admin UI; (4) Congestion on Verizon's network during peak hours (7–11 PM); (5) A deteriorating ONT reducing fiber throughput — run a wired speed test directly from the ONT Ethernet port to bypass the router; (6) DNS latency — switch to 8.8.8.8 or 1.1.1.1 for faster resolution.

How do I check if Verizon has a network outage in my area?

Visit downdetector.com/status/verizon for real-time crowdsourced outage reports. Use the official Verizon outage checker at verizon.com/support/outages/ for your service address. Open the My Verizon app, go to your account, and look for an 'Outages' or 'Network Status' banner. You can also run a traceroute (tracert 8.8.8.8 on Windows, traceroute 8.8.8.8 on Linux/macOS) to see exactly where packets are dropping — if loss occurs in the first two hops within Verizon's 10.x.x.x address space, it is a carrier-side outage.

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

Fix Verizon router issues including 'connected without internet', slow 5G/FiOS speeds, and no internet. Step-by-step diagnostic commands and solutions inside.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,702 words

Key Takeaways

Root cause #1: ONT (Optical Network Terminal) signal loss or misconfiguration — affects FiOS users and manifests as 'connected without internet' even with solid Wi-Fi signal.
Root cause #2: IP address lease failure or DNS misconfiguration — router obtains an APIPA address (169.254.x.x) instead of a valid WAN IP, causing 'no internet' on all connected devices.
Root cause #3: 5G NR band congestion or device firmware mismatch — explains why Verizon 5G appears slower than LTE/4G in certain areas or on certain hardware.
Root cause #4: Router firmware bug or corrupted DHCP table — causes intermittent drops and 'connected but no internet' errors on Verizon Home Router (G3100, CR1000A) devices.
Quick fix summary: Power-cycle ONT → reboot router → release/renew DHCP → change DNS to 8.8.8.8 → check for firmware updates → contact Verizon if ONT light is solid red.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle ONT + Router	First step for any Verizon internet outage or 'connected without internet'	5 min	None
Release/Renew DHCP on router	Router shows 169.254.x.x WAN IP or 0.0.0.0 — IP lease failure	2 min	Brief disconnection
Change DNS servers (8.8.8.8 / 1.1.1.1)	Internet loads some sites but not others; DNS-specific failures	2 min	Very low
Factory reset Verizon router	Persistent 'no internet' after all soft fixes; corrupted config	15 min	Erases all custom settings
Update router firmware via My Fios app	Slow speeds or repeated drops on G3100/CR1000A models	10 min	Low — auto-backup available
Force LTE/4G band on mobile device	Verizon 5G slower than 4G in congested or fringe 5G area	1 min	None
Replace or re-provision ONT	ONT indicator shows solid red or no light after 15+ min reboot	30–120 min	Requires Verizon tech or self-install kit
Run Verizon network diagnostic tool	Intermittent outages with no clear hardware fault	5 min	None

Understanding Verizon Router & Internet Problems

Verizon's home internet infrastructure — whether FiOS fiber, DSL, or 5G Home Internet — involves multiple layers that must all function correctly before data reaches your browser. When any layer fails, users see one of these common symptoms:

"Wi-Fi connected, no internet" — device connects to the router but the router has no WAN connectivity
"No Verizon internet" — complete service loss, often an ONT or upstream issue
"Verizon 5G slower than 4G" — band steering or congestion problem
"Verizon internet connected but no internet" — DHCP or DNS failure downstream of the router

Understanding which layer is broken saves hours of guesswork.

Layer 1: Physical / ONT (FiOS Users)

For FiOS subscribers, the Optical Network Terminal (ONT) converts fiber-optic light signals to electrical Ethernet or coaxial signals. The ONT is the single most common point of failure for complete Verizon FiOS outages.

ONT indicator light meanings:

Light	Color/State	Meaning
PON	Solid Green	Fiber signal established
PON	Blinking Green	Authenticating
PON	Solid Red	No fiber signal — physical issue
WAN	Solid Green	WAN link to router active
WAN	Off	No Ethernet link to router
Power	Off	No power to ONT

ONT Troubleshooting Steps:

Locate the ONT (usually a white box mounted on an exterior wall or in a utility closet).
Check the PON light. If solid red, the fiber strand may be broken, dirty, or disconnected at the junction box.
Inspect the SC/APC fiber connector on the ONT for bends or kinks in the cable.
Unplug the ONT power adapter for 60 seconds, then reconnect. Wait 3–5 minutes for PON to turn solid green.
If PON stays red after 10 minutes, call Verizon technical support — this requires a field technician to restore the fiber signal.

Layer 2: Router WAN IP Assignment (DHCP)

Even when the ONT is healthy, the router must obtain a valid WAN IP address from Verizon's DHCP servers. Failure here produces the frustrating "connected without internet" state.

How to check the WAN IP on a Verizon router:

Open a browser and navigate to http://192.168.1.1 (default gateway for most Verizon routers).
Log in with your credentials (default: admin / password, or printed on the router label).
Go to My Network → Network Connections → Broadband Connection.
Look at the IP Address field. If it reads 0.0.0.0 or 169.254.x.x, the router has not received a valid WAN IP.

Fix: Force DHCP renewal

In the router UI: My Network → Network Connections → Broadband Connection → Settings → Release then Renew.
Alternatively, power-cycle the router by unplugging it for 30 seconds.

If renewal repeatedly fails:

Check that the Ethernet cable between the ONT and the router WAN port is firmly seated.
Try a different Cat5e/Cat6 cable.
Confirm the ONT WAN light is solid green.
Call Verizon to verify your account is active and the MAC address on file matches your router's WAN MAC.

Layer 3: DNS Resolution Failures

A router can have a valid WAN IP but fail to resolve domain names, producing errors like:

ERR_NAME_NOT_RESOLVED in Chrome
DNS_PROBE_FINISHED_NO_INTERNET
Sites accessible by IP (e.g., http://8.8.8.8) but not by hostname

Fix: Override DNS on your device or router

On Windows (CMD as Administrator):

ipconfig /flushdns
netsh interface ip set dns "Wi-Fi" static 8.8.8.8
netsh interface ip add dns "Wi-Fi" 1.1.1.1 index=2

On macOS (Terminal):

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
sudo networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1

On the Verizon router UI: My Network → Network Connections → Broadband Connection → Settings → DNS — enter 8.8.8.8 and 1.1.1.1.

Layer 4: Verizon 5G Home Internet or Mobile 5G Performance Issues

Verizon 5G (both Ultra Wideband mmWave and Nationwide Sub-6 GHz) can test slower than LTE under real-world conditions:

Why Verizon 5G is slower than 4G:

Nationwide 5G (Sub-6 GHz / DSS) uses Dynamic Spectrum Sharing with LTE, which can reduce peak speeds below pure LTE throughput.
mmWave 5G has extremely limited range (300–500 feet) and is blocked by walls, weather, and foliage. If your device shows 5G but you're barely in range, throughput collapses.
5G tower congestion — densely populated areas can saturate 5G capacity despite advertised speeds.
Device modem firmware — older firmware on Pixel, Samsung, or iPhone devices may mishandle carrier aggregation.

Fix for slow Verizon 5G on Android:

Go to Settings → Network & Internet → Mobile Network → Preferred network type → temporarily select LTE to confirm if LTE is indeed faster.
If LTE is faster, report the 5G performance issue to Verizon via the My Verizon app → Support → Network Issue.

Fix for Verizon 5G Home Internet (LTE/5G gateway like ASK-NCQ1338):

Physically relocate the gateway to a window facing the nearest Verizon tower (use the My Verizon app → 5G Home → Signal Meter to optimize placement).
Run an Ethernet cable from the gateway to your device for baseline speed testing before blaming Wi-Fi.

Layer 5: Router Firmware and Hardware Faults

Verizon's CR1000A (Wi-Fi 6E) and G3100 (Wi-Fi 6) routers occasionally develop bugs that cause DHCP table corruption or wireless association failures.

Check firmware version:

Router admin UI → System Settings → Advanced → System Information → Firmware Version
Compare against the latest version listed in the Verizon FiOS router release notes.

Forced firmware update via CLI (SSH if enabled):

ssh admin@192.168.1.1
show version
request system software upgrade

Factory reset as last resort:

Locate the reset pinhole on the back of the Verizon router.
With the router powered on, hold reset for 15 seconds using a paperclip.
Release when all LEDs flash simultaneously.
Wait 5 minutes for the router to reinitialize.
Reconnect using default credentials and re-enter your Wi-Fi SSID/password.

Warning: Factory reset erases all port forwarding rules, custom DNS settings, Wi-Fi credentials, and parental controls.

Layer 6: Verizon Network Outages (Not Your Equipment)

Before spending hours on local troubleshooting, always check whether the issue is upstream:

Visit downdetector.com/status/verizon to see real-time community outage reports.
Check the Verizon Service Outage page: https://www.verizon.com/support/outages/
Use the My Verizon app → tap your account → Outages to see localized impact.
Run a traceroute to confirm where packets are dropping (see code block section below).

If the traceroute shows packet loss at the first or second hop (10.x.x.x addresses within Verizon's network), it is a carrier-side issue and local fixes will not help — open a support ticket and wait for resolution.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# =============================================================
# Verizon Router & Internet Diagnostic Script
# Run on a Linux/macOS client connected to the Verizon network
# For Windows, equivalent commands are noted in comments
# =============================================================

echo "===== VERIZON INTERNET DIAGNOSTICS =====\n"

# --- 1. Check local IP and default gateway ---
echo "[1] Local network configuration:"
if command -v ip &>/dev/null; then
  ip addr show | grep -E 'inet |link/ether'
else
  ifconfig | grep -E 'inet |ether'
fi
# Windows equivalent: ipconfig /all

echo ""

# --- 2. Check default gateway reachability ---
GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
echo "[2] Pinging default gateway ($GATEWAY):"
ping -c 4 "$GATEWAY" 2>/dev/null || echo "Gateway unreachable — check router or cable"
# Windows: ping 192.168.1.1

echo ""

# --- 3. DNS resolution test ---
echo "[3] DNS resolution test (Verizon default DNS vs Google):"
echo "  Verizon DNS:"
time dig @4.2.2.1 google.com +short +time=3 2>/dev/null || echo "  Verizon DNS failed or slow"
echo "  Google DNS:"
time dig @8.8.8.8 google.com +short +time=3 2>/dev/null || echo "  Google DNS unreachable"
echo "  Cloudflare DNS:"
time dig @1.1.1.1 google.com +short +time=3 2>/dev/null || echo "  Cloudflare DNS unreachable"
# Windows equivalent: nslookup google.com 8.8.8.8

echo ""

# --- 4. Traceroute to detect where the path breaks ---
echo "[4] Traceroute to 8.8.8.8 (first 10 hops):"
traceroute -m 10 -q 2 8.8.8.8 2>/dev/null || tracepath -m 10 8.8.8.8 2>/dev/null
# Windows: tracert -h 10 8.8.8.8
# Look for: first hop = 192.168.1.1 (router)
#           second hop = 10.x.x.x (Verizon CPE/BRAS)
#           packet loss at hop 2+ = carrier issue

echo ""

# --- 5. Speed test via CLI (requires speedtest-cli) ---
echo "[5] Running speed test (requires speedtest-cli):"
if command -v speedtest-cli &>/dev/null; then
  speedtest-cli --simple
else
  echo "  speedtest-cli not installed. Install with: pip install speedtest-cli"
  echo "  Or run manually at: fast.com or speedtest.net"
fi

echo ""

# --- 6. Check DHCP lease on client ---
echo "[6] Current DHCP lease details:"
cat /var/lib/dhcp/dhclient.leases 2>/dev/null | tail -20 \
  || cat /var/lib/dhcpcd/*.lease 2>/dev/null | tail -20 \
  || echo "  Lease file not found at standard paths. Check: /var/lib/dhcp/ or /var/lib/NetworkManager/"
# Windows: ipconfig /all | findstr "DHCP"

echo ""

# --- 7. Force DHCP release and renew on Linux ---
echo "[7] Force DHCP renew (requires root/sudo):"
INTERFACE=$(ip route | grep default | awk '{print $5}' | head -1)
echo "  Detected interface: $INTERFACE"
if [ "$(id -u)" -eq 0 ]; then
  dhclient -r "$INTERFACE" && echo "  DHCP lease released."
  sleep 2
  dhclient "$INTERFACE" && echo "  DHCP lease renewed."
else
  echo "  Run as root to execute: sudo dhclient -r $INTERFACE && sudo dhclient $INTERFACE"
fi
# Windows: ipconfig /release && ipconfig /renew

echo ""

# --- 8. Flush DNS cache ---
echo "[8] Flush DNS cache:"
if command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches && echo "  systemd-resolved cache flushed."
elif [ -f /etc/init.d/nscd ]; then
  sudo /etc/init.d/nscd restart && echo "  nscd restarted."
else
  echo "  Manual flush: sudo systemctl restart systemd-resolved"
fi
# macOS: sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
# Windows: ipconfig /flushdns

echo ""

# --- 9. Test HTTP connectivity ---
echo "[9] HTTP/HTTPS connectivity check:"
curl -o /dev/null -s -w "  HTTP status for http://google.com: %{http_code} (time: %{time_total}s)\n" http://google.com
curl -o /dev/null -s -w "  HTTPS status for https://google.com: %{http_code} (time: %{time_total}s)\n" https://google.com
# If HTTP works but HTTPS fails: check system clock sync (timedatectl status)
# If both fail after DNS resolves: check firewall rules

echo ""
echo "===== DIAGNOSTICS COMPLETE ====="
echo "Next steps based on results:"
echo "  - Gateway unreachable   → power-cycle router and ONT"
echo "  - WAN IP is 169.254.x.x → DHCP lease failure, contact Verizon"
echo "  - Packet loss at hop 2  → Verizon carrier outage, check downdetector.com"
echo "  - DNS fails, HTTP by IP works → switch DNS to 8.8.8.8"
echo "  - All passes but slow  → run speedtest and check for QoS/firmware issues"

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing ISP-level connectivity failures, home networking infrastructure, and carrier-grade equipment. Our guides are based on hands-on lab testing, real incident postmortems, and verified vendor documentation. We specialize in translating complex network diagnostics into actionable steps for both technical and non-technical audiences.

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.