Why does my Verizon router say 'No Internet' even though all the lights are green?

Green lights on the router indicate the device has power and a local network is active, but they don't confirm a valid WAN connection. Open the gateway admin panel at 192.168.1.1 and check if the WAN IP is 0.0.0.0 or blank — this means DHCP failed and Verizon hasn't assigned a public IP. Try a sequential reboot of the ONT and router. If the WAN IP is valid (e.g., 96.x.x.x) but internet still fails, the issue is likely a routing or DNS problem on either the gateway or your device.

My Verizon FiOS internet went out suddenly with no changes — what should I check first?

First, check Verizon's outage map at verizon.com/support/outage-page. If no outage is reported, check the ONT's PON LED — if it's red or off, there's a fiber signal issue (possible fiber cut or ONT hardware failure). If the PON LED is green but the Data LED is off or amber, check the Ethernet cable between the ONT and your router's WAN port. A sudden outage with no user changes is most commonly caused by a Verizon network event, ONT firmware update glitch, or physical cable fault.

How do I fix 'Verizon Internet Gateway No Internet Connection' on the CR1000A or G3100 specifically?

For the CR1000A and G3100: (1) Log into 192.168.1.1 and verify WAN status under 'Connection > WAN' or 'My Network > Broadband Connection'. (2) If WAN IP shows 0.0.0.0, perform a sequential reboot — power off the gateway, wait 90 seconds, power back on. (3) If the issue persists after two reboots, check for a pending firmware update in the gateway settings. (4) As a last resort, factory reset using the pinhole button. Both devices also support the My Verizon app diagnostics tool, which can send a remote provisioning signal to the gateway.

My Verizon 5G Home Internet shows no internet connection — is it different from FiOS troubleshooting?

Yes. Verizon 5G Home Internet uses a cellular gateway (not fiber/ONT), so the ONT steps don't apply. Key differences: (1) Check the signal strength indicator on the gateway — low bars mean poor 5G signal. Try repositioning the gateway near a window or higher elevation. (2) Check for local 5G tower outages via the Verizon app. (3) Power-cycle by unplugging for 60 seconds. (4) Ensure the SIM card inside the gateway is seated properly (visible after removing the base panel). If signal strength is permanently low, contact Verizon to discuss antenna placement options or a signal extender.

Why does my Verizon router keep dropping internet every few hours?

Intermittent drops every few hours usually indicate one of three things: (1) DHCP lease renewal failure — the router fails to renew its WAN IP every 24 hours; check router logs at 192.168.1.1 for DHCP timeout events. (2) Thermal throttling — the gateway is overheating; ensure it has 6+ inches of ventilation on all sides and is not enclosed in a cabinet. (3) Fiber signal degradation — marginal fiber signal that passes most of the time but fails under temperature or load conditions; Verizon can run an optical power meter test on your line. Also check for loose coax or Ethernet connections at the ONT and router.

No Internet on Verizon: Fix 'Verizon Internet Gateway No Internet Connection' Error (2024)

Fix Verizon no internet connection errors on FiOS and 5G Home. Step-by-step guide covering router resets, ONT checks, DNS fixes, and gateway troubleshooting.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,442 words

Key Takeaways

Root cause 1: ONT (Optical Network Terminal) or gateway device has lost sync with Verizon's network due to fiber signal loss, firmware glitch, or physical cable fault.
Root cause 2: DHCP lease failure or DNS misconfiguration causing the router to show 'connected' locally but with no WAN IP assigned, resulting in 'No Internet Access' status.
Root cause 3: Verizon network outage or provisioning issue on the ISP side, including account suspension or line maintenance, that blocks WAN connectivity regardless of local hardware state.
Quick fix summary: Power-cycle your ONT and router in sequence (ONT first, wait 2 minutes, then router), verify WAN IP assignment in the gateway admin panel at 192.168.1.1, run DNS flush commands, and check Verizon's outage map before escalating to Tier 2 support.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle ONT + Router (sequential)	First step for any sudden no-internet event; clears transient firmware or DHCP state issues	5–10 min	None
Factory reset Verizon gateway/router	Persistent no-internet after multiple reboots; suspected config corruption	15–30 min	Medium – wipes all custom settings, Wi-Fi passwords, port forwards
Manual DNS override (8.8.8.8 / 1.1.1.1)	Internet works intermittently or pages fail to resolve but ping to IP succeeds	2–5 min	Low
Re-provision via My Verizon portal	Account or line changes recently made; device shows 'Not Activated' or 'Provisioning Error'	10–20 min	Low
Check and reseat coax/fiber/Ethernet cables	Physical signal loss, ONT shows red or amber light, or after construction/move	5–15 min	None
Update gateway firmware manually	After Verizon firmware rollout fails or device is stuck on outdated build	20–40 min	Low-Medium
Replace ONT or gateway hardware	All other steps fail; hardware diagnostics show persistent faults or defective unit	1–2 hours (tech visit)	Low (ISP handles)

Understanding the 'No Internet' Error on Verizon

When your Verizon router or gateway shows a 'No Internet Connection' warning — whether it appears as a yellow triangle on Windows, an exclamation mark on Android, or the gateway admin page reports 'WAN Status: Disconnected' — the underlying cause is that your device has a local LAN/Wi-Fi connection but cannot reach Verizon's WAN (Wide Area Network). This is a distinct failure from a Wi-Fi password issue or a local device misconfiguration.

Verizon FiOS uses a fiber-to-the-premises (FTTP) architecture where an Optical Network Terminal (ONT) converts the fiber signal to an Ethernet or coaxial signal fed into your router (e.g., Verizon G3100, CR1000A, or older ActionTec MI424WR). Verizon 5G Home Internet skips the ONT and uses a cellular 5G gateway (ASK-NCQ1338, Arcadyan KVD21). Each architecture has different failure points.

Common Error Messages You May See

Windows Network Status: "No Internet Access" or "No Internet, Secured"
Gateway Admin Panel (192.168.1.1): "WAN IP: 0.0.0.0" or "Internet Connection: Disconnected"
Verizon App: "Your gateway is offline" or "Unable to connect to the internet"
Browser: ERR_NAME_NOT_RESOLVED, ERR_INTERNET_DISCONNECTED
ONT LED: Solid red or blinking amber on the 'PON' or 'Data' indicator
Router WAN LED: Off or solid amber/red instead of solid green

Step 1: Identify the Failure Layer

Before touching any hardware, determine where the failure is occurring:

1a. Check Verizon's Outage Map Visit https://www.verizon.com/support/outage-page/ or the My Verizon app. Search your ZIP code. If there's a known outage, your only action is to wait. Note the estimated restoration time and open a ticket for a service credit.

1b. Check ONT Status Lights (FiOS only) Locate the ONT box (usually mounted on an exterior wall or in a utility closet). Interpret the LEDs:

PON light Green: Fiber signal established. Problem is downstream.
PON light Red/Off: Fiber signal lost. Check fiber cable for kinks, bends over 90°, or physical damage. Call Verizon if cable appears intact.
Data/Ethernet light Green: ONT is passing traffic to router.
Data/Ethernet light Off: ONT has signal but isn't communicating with router — check the Ethernet cable between ONT and router WAN port.

1c. Check Gateway WAN IP Open a browser and navigate to http://192.168.1.1 (default for most Verizon gateways). Log in with admin credentials (printed on the router label or default: admin/password). Navigate to:

FiOS G3100: My Network > Network Connections > Broadband Connection
CR1000A: Connection > WAN
5G Home Gateway: Status > Internet

If the WAN IP shows 0.0.0.0 or is blank, DHCP negotiation has failed — the router is not getting an address from Verizon.

Step 2: Power-Cycle in the Correct Sequence

A sequential reboot clears DHCP state, forces re-authentication with Verizon's RADIUS/DHCP servers, and resets the ONT's optical parameters.

For Verizon FiOS:

Unplug the ONT's power adapter (or flip its circuit breaker if hardwired).
Unplug the Verizon router/gateway power cable.
Wait 2 full minutes — this ensures Verizon's DSLAM/OLT (Optical Line Terminal) deregisters the ONT.
Plug the ONT back in. Wait for the PON and Data LEDs to turn solid green (can take 60–90 seconds).
Plug the router back in. Wait 3–5 minutes for it to fully boot and negotiate a WAN IP.
Re-check the gateway admin panel for a valid WAN IP (e.g., 96.x.x.x or 108.x.x.x for Verizon FiOS).

For Verizon 5G Home Gateway:

Power off the gateway using the power button or by unplugging.
Wait 60 seconds.
Power back on and wait 5–10 minutes for 5G signal acquisition (the signal bars on the device should illuminate).

Step 3: Diagnose at the OS Level

If the gateway shows a valid WAN IP but internet still doesn't work on specific devices, the issue is client-side.

On Windows (Run as Administrator):

ipconfig /all
pathping 8.8.8.8
nslookup google.com 8.8.8.8

Look for: Default Gateway populated, DNS Servers listed, and successful ping/traceroute to 8.8.8.8.

Common finding: DHCP Lease Obtained: never or Default Gateway: blank means your device isn't getting a LAN IP from the router. Fix: disable and re-enable the network adapter, or run ipconfig /release && ipconfig /renew.

DNS-specific failure: ping 8.8.8.8 succeeds but ping google.com fails — classic DNS failure. Override DNS in your network adapter settings or router to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

Step 4: Advanced — Reset Network Stack

If reboots and DNS changes don't resolve the issue, corrupted network stack entries on Windows can mimic an internet outage:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew

Reboot after running these commands.

Step 5: Factory Reset the Verizon Gateway (Last Resort)

If the gateway admin panel shows a valid WAN IP but internet still doesn't pass through, a factory reset may clear corrupted NAT, firewall, or routing table entries.

Warning: This will erase all custom settings including Wi-Fi SSIDs, passwords, port forwarding rules, and DMZ configurations.

Locate the reset pinhole on the back of the router.
With the device powered on, press and hold the reset button with a paperclip for 10–15 seconds until the LEDs flash.
Wait 5 minutes for the factory restore to complete.
Reconfigure Wi-Fi and re-run the Verizon setup wizard if prompted.

Step 6: Escalate to Verizon Support

If all local troubleshooting fails:

Call 1-800-VERIZON (1-800-837-4966) and request Tier 2 technical support.
Provide them with: account number, MAC address of your gateway (on the label), the ONT serial number, and the troubleshooting steps you've already taken.
Request a line test and ask them to check for provisioning status on your ONT — sometimes a backend reprovisioning push fixes issues without a technician visit.
If the ONT or gateway hardware is confirmed faulty, Verizon will schedule a technician visit (typically free if hardware is within warranty or a FiOS-provided device).

Frequently Asked Questions

bash

#!/usr/bin/env bash
# ============================================================
# Verizon No Internet Diagnostic Script
# Compatible with: macOS, Linux (run with bash)
# For Windows: use equivalent commands in PowerShell/CMD
# ============================================================

echo "=== Verizon No Internet Diagnostic Tool ==="
echo "Timestamp: $(date)"
echo ""

# --- 1. Check local IP and gateway ---
echo "[1] Local Network Configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  GATEWAY=$(netstat -nr | grep '^default' | awk '{print $2}' | head -1)
  LOCAL_IP=$(ipconfig getifaddr en0 2>/dev/null || ipconfig getifaddr en1 2>/dev/null)
else
  GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
  LOCAL_IP=$(hostname -I | awk '{print $1}')
fi
echo "  Local IP     : ${LOCAL_IP:-NOT ASSIGNED - DHCP failure suspected}"
echo "  Gateway IP   : ${GATEWAY:-NOT FOUND - check router connection}"
echo ""

# --- 2. Ping local gateway ---
echo "[2] Pinging Local Gateway (${GATEWAY}):"
if ping -c 3 -W 2 "$GATEWAY" > /dev/null 2>&1; then
  echo "  PASS - Gateway is reachable (LAN is working)"
else
  echo "  FAIL - Cannot reach gateway. Check physical cable or Wi-Fi connection."
fi
echo ""

# --- 3. Ping Verizon DNS server ---
echo "[3] Pinging Verizon DNS (4.2.2.1):"
if ping -c 3 -W 3 4.2.2.1 > /dev/null 2>&1; then
  echo "  PASS - WAN connectivity confirmed via Verizon DNS IP"
else
  echo "  FAIL - Cannot reach 4.2.2.1. WAN connection is down."
fi
echo ""

# --- 4. Ping Google DNS (bypass ISP DNS) ---
echo "[4] Pinging Google DNS (8.8.8.8):"
if ping -c 3 -W 3 8.8.8.8 > /dev/null 2>&1; then
  echo "  PASS - Internet reachable by IP. Issue is DNS resolution only."
else
  echo "  FAIL - Cannot reach 8.8.8.8. Full internet outage confirmed."
fi
echo ""

# --- 5. DNS resolution test ---
echo "[5] DNS Resolution Test:"
if nslookup google.com 8.8.8.8 > /dev/null 2>&1; then
  echo "  PASS - DNS resolving via 8.8.8.8"
else
  echo "  FAIL - DNS resolution failed even with Google DNS"
fi

if nslookup google.com > /dev/null 2>&1; then
  echo "  PASS - Default DNS resolving correctly"
else
  echo "  FAIL - Default DNS (router/Verizon) not resolving. Override DNS to 8.8.8.8 or 1.1.1.1"
fi
echo ""

# --- 6. Traceroute to detect where packets drop ---
echo "[6] Traceroute to 8.8.8.8 (first 10 hops):"
traceroute -m 10 -w 2 8.8.8.8 2>/dev/null || tracert -h 10 8.8.8.8 2>/dev/null || echo "traceroute not available"
echo ""

# --- 7. Check gateway admin reachability ---
echo "[7] Verizon Gateway Admin Panel:"
curl -s --max-time 3 http://192.168.1.1 -o /dev/null -w "  HTTP Status: %{http_code}\n" || echo "  Cannot reach gateway admin at 192.168.1.1"
echo ""

# --- 8. Flush DNS cache (Linux/macOS) ---
echo "[8] Flushing local DNS cache:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "  DNS cache flushed (macOS)"
elif command -v systemctl &> /dev/null; then
  sudo systemctl restart systemd-resolved 2>/dev/null && echo "  DNS cache flushed (systemd-resolved)"
else
  echo "  Manual flush required on this system"
fi
echo ""

# --- Windows equivalent commands (for reference) ---
# Run these in Windows CMD as Administrator:
# ipconfig /release
# ipconfig /flushdns
# ipconfig /renew
# netsh winsock reset
# netsh int ip reset
# (Reboot after running)

echo "=== Diagnostic Complete ==="
echo "If WAN is down, perform sequential ONT+router reboot."
echo "If DNS only, set adapter DNS to 8.8.8.8 and 1.1.1.1."
echo "Check outages: https://www.verizon.com/support/outage-page/"

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, managing carrier-grade networks, and writing actionable troubleshooting documentation. Our guides are tested against real hardware environments and updated regularly to reflect current firmware versions and ISP infrastructure changes.

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.