WiFi Connected But No Internet?

Wi-Fi can stay connected even when internet access fails. Start with four fast checks, then use Windows, Mac, iPhone, Android, Chromebook or Smart TV steps to isolate DHCP, DNS, gateway, router or ISP faults.

Connected but not online

Wi-Fi Connected but No Internet? Find the Failed Layer

Use four fast checks first, then compare the device, router gateway, DHCP, DNS, Ethernet and provider path to find the first point where internet access fails.

Reviewed by: LinkSpeed Editorial TeamLast reviewed: 8 August 2026Device paths checked against Microsoft, Apple, Android and ChromeOS guidance.How LinkSpeed tests
Network diagram illustrating a device connected to a local Wi-Fi router while upstream internet access is checked through DHCP, DNS, an Openreach ONT and the ISP

Quick fix checklist

Wi-Fi connected but no internet? Try these four fixes first

These are the safest high-yield checks before deeper DNS, DHCP or adapter changes. Do not factory-reset the router.

1

Restart the router and device

Save work, restart the phone or computer, then power the router off for 30 seconds and let it fully reconnect. On full fibre, photograph unusual ONT lights before restarting anything.

2

Toggle Airplane Mode

Turn Airplane Mode on for 10 seconds, then turn it off. This forces the device to rebuild its Wi-Fi connection without changing saved settings.

3

Forget and rejoin Wi-Fi

Forget the saved network, reconnect and enter the password again. This clears a stale Wi-Fi profile, cached security state or bad lease association.

4

Check for an ISP outage

Use mobile data to check your ISP (Internet Service Provider) outage or status page. If every home device is offline, the fault may be outside your Wi-Fi network.

DeviceWi-FiRouter / DHCP / DNSONT / ISP
Still no internet? Jump to your device:Windows 11/10MaciPhone / iPadAndroid

Start here

The three comparisons that locate most connected-but-offline faults

Do not reset everything at once. Start by proving the scope, then check whether the device can reach the router and whether the router can reach the internet.

1

Another device works

The broadband service is probably available. Focus on the affected device, saved network profile, DHCP lease, DNS, VPN or clock.

2

Every device is offline

The router, ONT, WAN cable, provider session or external service is the first suspect rather than one device.

3

Router page opens, websites do not

The local Wi-Fi path is working. Check the router’s internet status, DNS, captive portal, VPN or provider service.

Interactive check

Locate the likely fault boundary from one visible clue

Select the state that best matches the connection now. The result gives you the next diagnostic section rather than claiming a final cause from one clue.

Whole Home Offline?Run Ping TestWebsites Only Failing?

Quick reference

Match the visible symptom to the next useful check

Symptoms, likely cause and first diagnostic step are combined here so you can move directly from the message on screen to useful evidence.

Only one device says no internet

A stale saved network, DHCP lease, DNS cache, VPN, Private Relay, security software or incorrect device time is more likely than a broadband outage.

Next: forget and rejoin Wi-Fi, then compare the same device with another network.

Every device is connected but offline

The router can still broadcast Wi-Fi after losing its broadband session. A WAN cable, ONT, router authentication or provider fault is more likely.

Next: check router and ONT service lights, test Ethernet, then use the broadband-down guide. Run the ping test only when some external traffic returns.

Apps work but websites do not

The core connection is carrying traffic, so the fault is more likely at the DNS, browser, filtering or certificate layer.

Next: use the websites-not-loading diagnostics guide rather than repeating the browser-layer checks here.

The address starts 169.254

The device has created an APIPA fallback because it did not receive a usable DHCP address from the router.

Next: renew the lease, forget the network and check whether other devices also fail to obtain an address.

Public Wi-Fi never shows the login page

A captive portal may be blocked by VPN, Private Relay, custom DNS or HTTPS-only behaviour.

Next: temporarily disable those services and open a plain HTTP page to trigger the login screen. If the fault consistently follows the VPN, use the VPN troubleshooting checklist.

FTTP devices are offline and ONT lights changed

The Wi-Fi radio may be healthy while the optical handoff or Ethernet link to the router has failed.

Next: record LOS, PON and LAN/PORT lights before restarting anything.
↑ Back to guide index

Test in order

Locate the first failed layer

Keep the same device and change one variable at a time. The first failed comparison tells you which section to use.

  1. Compare another device on the same Wi-Fi.

    If the second device works, keep the investigation on the original device. If both fail, continue towards the router and broadband path.

  2. Try more than one website and one app.

    Apps working while websites fail points towards DNS, browser, filtering or certificate problems rather than a total outage.

  3. Open the router gateway.

    Try the router admin address shown by your device, commonly 192.168.1.1 or 192.168.1.254. If it opens, the local Wi-Fi link is working.

  4. Check the device IP address and clock.

    A 169.254.x.x address indicates APIPA. Also set date, time and time zone to update automatically so secure certificate checks can succeed.

  5. Remove captive-portal and privacy detours.

    On guest Wi-Fi, temporarily disable VPN, custom DNS or Private Relay and open a plain HTTP page. On home Wi-Fi, compare with those services paused.

  6. Compare Ethernet and inspect router or ONT lights.

    Ethernet working isolates the problem to Wi-Fi or the device. Ethernet failing across devices moves the fault to the router, ONT, WAN cable or provider.

  7. Check provider status and preserve evidence.

    Use mobile data to check the provider status page. Record device scope, light colours, gateway access and Ethernet results before support changes anything.

↑ Back to guide index

Diagnostic next step

If the connection partly works, test whether it is stable

If some apps or websites still load, run the LinkSpeed browser-based ping stability test. A stable result while website names fail points more strongly towards DNS or browser handling; repeated request failures across services suggest a wider connectivity problem. If nothing external loads at all, skip these tests and continue with the router, ONT and provider checks.

Run Live Ping TestCheck Packet LossCheck ONT Lights
↑ Back to guide index

Message reference

What common connected-but-offline messages usually indicate

Use the wording on screen as a clue, not a final diagnosis. Confirm it with another device and the router or Ethernet checks.

Device or contextTypical messageLikely bottleneckBest next action
Windows 10 or 11No Internet, SecuredStale DNS or DHCP state, VPN/security conflict, or router broadband loss.Forget and reconnect to Wi-Fi; if needed, run ipconfig /flushdns and ipconfig /renew.
iPhone, iPad or MacNo Internet ConnectionPrivate Wi-Fi Address, Private Relay, VPN, stale lease or captive portal loop.Renew the lease, compare with VPN or Private Relay paused, and test another device.
Android or smart TVConnected, cannot provide internetClock mismatch, saved-network corruption, DNS failure, weak Wi-Fi or router WAN loss.Set time automatically, forget and rejoin the network, then compare another device in the same room.
Public or guest Wi-FiRedirect or login never appearsCaptive portal blocked by VPN, custom DNS, Private Relay or HTTPS-only behaviour.Open a plain HTTP page in a clean browser tab to trigger the portal.
Full-fibre home lineAll devices connected but offlineONT optical sync, WAN cable or router authentication fault.Record ONT LOS, PON and LAN/PORT lights before restarting the router.

APIPA clue: an address beginning 169.254 means the device has not obtained a normal DHCP address from the router.

↑ Back to guide index

Device-specific fixes

Fix Wi-Fi connected but no internet on Windows, Mac, iPhone, Android, Chromebook and Smart TVs

Use the section for the affected device only. Menu labels can vary slightly by operating-system release or Android manufacturer.

Windows 11 and Windows 10

  1. Open Settings → Network & internet → Wi-Fi → Manage known networks, select the network, choose Forget, then reconnect.
  2. Open Command Prompt (cmd) as administrator and run ipconfig. If the IPv4 address begins 169.254, DHCP has failed. If Windows reports Default Gateway Unavailable, check the gateway and adapter state.
  3. If the address or DNS state looks stale, run ipconfig /release, ipconfig /renew and ipconfig /flushdns.
  4. Open Advanced network settings to disable and re-enable the Wi-Fi adapter. If you use IPv4 manually, verify it is set to Obtain an IP address automatically (DHCP) unless your network requires a static address.
  5. Use Network reset only after the earlier checks; it removes and reinstalls network adapters and may require VPN software to be set up again.

Why this helps: Windows can show Wi-Fi as connected while a stale DHCP lease, DNS cache, adapter state or missing default gateway prevents internet routing.

macOS

  1. Open System Settings → Wi-Fi, select Details beside the network and use Forget This Network if the saved profile may be stale.
  2. In the same Details panel open TCP/IP and choose Renew DHCP Lease. Check that the IP and Router fields contain normal local addresses.
  3. Open DNS and remove an incorrect manual DNS server if you do not need it. A DNS server not responding fault can leave the Mac connected to Wi-Fi while websites fail.
  4. If the problem started after changing work/home settings, use System Settings → Network → Locations to test a clean network location without destroying the original setup.
  5. On a managed or captive-portal network only, compare the network with Private Wi-Fi Address set as required by that network. Normally leave the privacy feature enabled.

Why this helps: renewing DHCP and separating saved-location, DNS and private-address settings distinguishes a Mac configuration fault from the router or ISP.

iPhone and iPad

  1. Turn Airplane Mode on for 10 seconds, then turn it off and reconnect to Wi-Fi.
  2. Go to Settings → Wi-Fi, tap the network, choose Forget This Network, then reconnect.
  3. On hotel, airport or guest Wi-Fi, pause VPN or Private Relay temporarily and open a plain HTTP page if the captive portal login does not appear.
  4. If the network authorises devices by MAC address, check Private Wi-Fi Address for that network. Change it only when the network operator requires a fixed or hardware address.
  5. Use Settings → General → Transfer or Reset iPhone/iPad → Reset → Reset Network Settings only after the simpler steps. This removes saved Wi-Fi networks and other network settings.

Why this helps: iOS can remain associated with the access point while a saved profile, captive portal, VPN/Private Relay path or network configuration blocks internet traffic.

Android phones and tablets

  1. Open Settings → Network & internet → Internet (wording varies by manufacturer), forget the saved Wi-Fi network and reconnect.
  2. Open the network details and check IP settings. Use DHCP unless the network administrator gave you a static address; a wrong static address can create an IP address conflict or unusable gateway.
  3. On public Wi-Fi, pause VPN or custom DNS temporarily and trigger the captive portal in a browser.
  4. If the venue registers devices by MAC address, compare the network privacy/MAC option with the venue's requirement. Restore the privacy setting afterwards.
  5. If simpler steps fail, use the phone's Reset Wi-Fi / network settings option. The exact location varies by Android version and manufacturer, and it removes saved network state.

Why this helps: Android can report a healthy Wi-Fi association even when DHCP, a static-IP conflict, custom DNS, captive-portal state or the upstream router path is broken.

Chromebook

  1. Open Settings → Network → Wi-Fi → Known networks, remove the affected network, then reconnect.
  2. Open the built-in ChromeOS Diagnostics app and run the Connectivity tests. Expand IP configuration if you need to inspect the assigned address.
  3. Restart the Chromebook and compare the same Wi-Fi with another device. If another device works, keep the investigation on ChromeOS rather than the ISP.
  4. If Diagnostics reports a DNS issue, remove unusual manual DNS or proxy settings before changing the router.

Why this helps: ChromeOS Diagnostics can separate local Wi-Fi, IP configuration, DNS and Google-service connectivity without immediately resetting the whole home network.

Smart TVs, Fire TV, Roku and Apple TV

  1. Set the device date and time to automatic. A badly wrong clock can break secure app sign-in while Wi-Fi still appears connected.
  2. Forget and rejoin the home Wi-Fi network if the device offers that option, then restart the streaming device rather than factory-resetting it.
  3. Test the same device on a phone hotspot for a few minutes. If streaming works there, the device is probably healthy and the home router, Wi-Fi or ISP path needs attention.
  4. On hotel or guest Wi-Fi, remember that some streaming devices cannot easily complete a captive-portal login. Complete the venue sign-in on a supported device or follow the venue/device instructions instead of repeatedly resetting Wi-Fi.

Why this helps: the hotspot comparison separates a streaming-device problem from a home Wi-Fi or broadband fault without changing router-wide settings.

Menu paths reviewed against current Microsoft Support, Apple Wi-Fi settings, Apple iPhone/iPad troubleshooting, Android Help and ChromeOS Diagnostics.

↑ Back to guide index

Copy-paste command helper

Generate a safe Windows or Mac network command

Choose the operating system and the check you want to run. These commands inspect or refresh the device network state; they do not change router settings. Windows release/renew briefly interrupts the device connection.

Replace this with the gateway shown by your device if different.
ipconfig /all

↑ Back to guide index

UK hardware check

Check Openreach ONT and router lights before changing settings

If the whole home is offline, hardware lights can move the diagnosis away from the phone or laptop. Openreach ONT labels are fairly consistent, but router and Virgin Media Hub colours vary by model, so use the router result as triage rather than a definitive fault code.

Openreach ONT: PON, LOS and LAN/PORT

Use this only if your fibre box actually has PON/LOS labels. Some Openreach ONTs use different labels such as Optical.

Choose the lights you can see

The checker will suggest the next fault boundary without claiming a cable break or provider fault from one light alone.

Openreach ONT guidance cross-checked against BT's Openreach modem light guide. A solid green PON with LOS off normally means the fibre link is recognised; persistent red/flashing LOS or abnormal PON states need optical/service checks.

↑ Back to guide index

Advanced checks

Device, DHCP, DNS and full-fibre checks worth using after the basics

These details preserve the technical depth without interrupting the main fault-boundary workflow.

APIPA, DHCP and IP address conflict

A 169.254.x.x address is a self-assigned APIPA fallback. Forget and rejoin Wi-Fi, renew the lease and check whether the router’s DHCP service is issuing normal local addresses to other devices.

If the device was configured manually, set it to Obtain an IP address automatically (DHCP) unless the network administrator supplied a static address. Two devices using the same manual address can create an IP address conflict.

DNS server not responding

If apps or direct IP connections work but websites fail by name, the connection may be online while the DNS server is not responding. Remove an incorrect manual DNS entry, flush the local DNS cache where supported and retest more than one domain.

Continue with the websites-not-loading diagnostics guide for deeper DNS, browser and HTTPS checks.

Default gateway unavailable

The default gateway is normally the router address your device uses to leave the local network. If Windows reports Default Gateway Unavailable, or the gateway field is blank or unreachable, renew DHCP, re-enable the adapter and confirm the router gateway opens locally.

If several devices cannot reach the gateway, investigate the router rather than changing DNS.

Captive portals and guest networks

Guest networks can block all traffic until a splash page is accepted. VPNs, custom DNS and Private Relay can prevent the redirect.

Open a plain HTTP page in a clean tab and re-enable privacy services after the portal has completed.

Incorrect device date and time

A badly wrong clock can invalidate HTTPS certificates and app authentication while the Wi-Fi connection itself remains active.

Set date, time and time zone to automatic, then close and reopen the affected browser or app.

Full-fibre ONT and router handoff

A router may continue broadcasting Wi-Fi when the ONT has lost optical sync. Record LOS, PON and LAN/PORT lights and check the Ethernet lead from the ONT to the router WAN port.

Do not bend, pull or look into the end of a fibre lead. If LOS remains red or flashing, contact the broadband provider.

↑ Back to guide index

Apply the result

Use the fix that matches the completed comparison

Apply one route only after the tests identify the failed layer.

One device fails

Do: forget and rejoin Wi-Fi, restart the device, update its network driver or software and compare VPN or privacy services.

Retest: the same website and app on the same Wi-Fi.

APIPA or DHCP failed

Do: renew the lease, remove manual addressing conflicts and restart the router once if several devices are affected.

Retest: confirm the device receives a normal private address from the router.

Guest Wi-Fi login is blocked

Do: pause VPN, custom DNS or Private Relay and open a plain HTTP page to trigger the portal.

Retest: sign in, then restore privacy services.

Ethernet works but Wi-Fi does not

Do: use the unstable Wi-Fi guide for signal, channel, mesh and device checks.

Retest: the same device over Ethernet and Wi-Fi.

Every device and Ethernet fail

Do: check cables, router and ONT lights, provider status and the broadband-down guide.

Retest: after one controlled restart or provider line test.
↑ Back to guide index

Escalate with evidence

When to contact the provider or device support

Escalate only after the scope and first failed layer are clear.

Contact the broadband provider

Every device and Ethernet fail, router or ONT service lights are abnormal, the provider status page reports an ISP (Internet Service Provider) outage, or the router cannot establish its internet session.

Contact device or workplace support

Only one managed device fails, the issue follows a VPN or security profile, or the device cannot obtain a valid address while other devices work.

UK outage check: If every device is offline on BT, Virgin Media, Sky or TalkTalk, use mobile data to check the provider's own status service before resetting DNS or Wi-Fi settings. A Virgin Media Hub can keep broadcasting Wi-Fi even when the upstream broadband service is unavailable.

BT Service Status Virgin Media Status Sky Service Checker TalkTalk Status 
Hi Support,

My device(s) show Wi-Fi connected but cannot reach the internet.

Affected devices: [ONE DEVICE / ALL DEVICES]
Provider: [BT / VIRGIN MEDIA / SKY / TALKTALK / OTHER]
Hardware: [OPENREACH ONT / ISP ROUTER / VIRGIN MEDIA HUB]
Router gateway opens: [YES / NO]
Ethernet works: [YES / NO]
Device IP address: [ADDRESS]
Router / Openreach ONT / Virgin Media Hub light state: [DETAILS]
Provider status result: [DETAILS]

I tested another device, checked the router gateway and compared Ethernet. Please investigate the first failed layer shown above.
↑ Back to guide index

Focused answers

Wi-Fi connected but no internet FAQs

These answers match the FAQ structured data in the page head.

Why does my device say connected to Wi-Fi but no internet?

The device has joined the local Wi-Fi network but cannot reach the wider internet. Common causes include router broadband loss, DHCP or APIPA address faults, DNS failures, VPN or Private Relay loops, captive portal blocks, device clock errors and provider outages.

What should I check first for Wi-Fi connected but no internet?

Start by checking whether the fault affects one device or every device. Then try a website and an app, open the router gateway, check the device IP address and compare Wi-Fi with Ethernet.

What is an APIPA IP address and why does it stop internet access?

An APIPA address usually starts with 169.254.x.x. It appears when a device cannot get a normal local IP address from the router's DHCP server, so it may show Wi-Fi connected while being unable to route traffic to the internet.

How do I fix Windows No Internet, Secured?

Forget and reconnect to the Wi-Fi network, restart the device, flush DNS, renew the IP lease, check for VPN or security software conflicts and confirm whether other devices can use the same router.

Why do apps work but websites do not?

That pattern points towards DNS, browser cache, HTTPS inspection, Private Relay, VPN, content filtering or browser profile problems rather than a complete broadband outage.

What does DNS server not responding mean?

It means the device may still have a working Wi-Fi and internet path but cannot translate website names into IP addresses. Check manual DNS settings, flush the DNS cache where supported and compare more than one website or app.

What does Default Gateway Unavailable mean?

The device cannot reliably reach the router address used to send traffic outside the local network. Renew DHCP, re-enable the network adapter and confirm that the router gateway opens before changing DNS.

What do the PON and LOS lights mean on an Openreach ONT?

On Openreach ONTs that use PON and LOS labels, a solid green PON light with LOS off normally means the fibre link is recognised. PON flashing with LOS off can mean the ONT is verifying the connection. A red or flashing LOS light, PON off, or persistent abnormal combinations point towards the optical link or service and should be checked with the broadband provider.

Why is my Virgin Media Hub connected to Wi-Fi but there is no internet?

A Virgin Media Hub can continue broadcasting Wi-Fi even when its upstream broadband connection is unavailable. Check another device, compare Ethernet, review the Hub status light for your model and use Virgin Media’s service-status checker before changing device DNS or Wi-Fi settings.

When should I contact my broadband provider?

Contact the provider if every device fails, Ethernet also has no internet, router or ONT service lights show a line fault, or provider status checks confirm an outage outside the home network.

↑ Back to guide index

Next guides

Choose the guide that matches the remaining fault

Use the narrower guide rather than repeating those diagnostics here.

Build evidence when broadband is downUse this when every device and Ethernet are offline.Diagnose websites not loadingUse this when apps work but browsers or domains fail.Fix intermittent dropoutsUse this when the connection returns by itself.Stabilise Wi-FiUse this when Ethernet works but wireless devices fail.Run the live ping testCheck whether external requests return when service comes back.Understand packet lossUse this when requests fail intermittently rather than remaining fully offline.
↑ Back to guide index

Editorial review

Reviewed and maintained by the LinkSpeed Editorial Team. Testing, provider and comparison claims follow our broadband testing and editorial methodology.

How LinkSpeed tests and checks claims