Updated 27 September, 2026 · 10 min read
Contents
1-The Confusing Part
2-Isolate the Layer That’s Actually Broken
3-Why This Happens
4-The Router Setting Almost Nobody Checks
5-Step-by-Step Fix
6-Mesh WiFi Systems: A Different Set of Problems
7-Wrapping Up
8-FAQ
1. The Confusing Part
A full signal bar WIFI connection with zero Mbps on a speed test is a particular animal it’s not quite the same problem as a slow connection. While not getting any data throughput is obviously a problem, “not slow” implies there’s still a connection of some sort, whereas a WIFI connection with no associated data transfer is more like a door that’s both open and locked at the same time.
Flushing DNS instead of your router was the faster solution for me personally the last time the issue presented, since the connection itself was fine and it was the DNS lookup that was failing. It’s a good idea to consider before going through the more involved process of checking everything else, but not necessarily the only possible cause identifying what layer the connection is failing on is a good start.
2. Isolate the Layer That’s Actually Broken
In order of most to least likely, here are the three connection layers to isolate the problem on:
Device to router — is the connection from your device to the router itself failing?
Router to ISP — is the router failing to connect to the internet?
DNS — can domains be resolved, or is that failing as well?
To test the first layer, try pinging your router from your device — if you get a response, it’s a problem somewhere beyond that. To check the second layer, try pinging a public IP address directly, rather than a domain name — if that fails, your router is failing to connect to the internet, which is likely a separate problem from your local WiFi connection. If pinging a domain name works fine but a speed test is failing, the problem is in DNS resolution.
3. Why This Happens
Any of the following issues can cause this particular set of symptoms:
1-DNS resolution failure instead of a connectivity problem — which is much more common than most people realize
2-An IP conflict on your network, preventing device communication
3-An outage on your ISP’s end, which is possible despite a seemingly fine local connection, since only the WiFi link is being measured
4-A failed upstream connection on your router despite a fine local connection, which is what the ping test in the previous section helps identify
5-CGNAT problems in some ISPs, discussed in the next section
4. The Router Setting Almost Nobody Checks
The thing about most home routers is that they have a “WAN” status page, often available by visiting the local IP address of the router in a web browser, that shows the status of the connection to your ISP — separately from any WiFi settings. This is useful, because it shows if your router has a valid public IP or not, which is a strong signifier of whether it has a working connection to the internet. Many ISPs are starting to use CGNAT (Carrier-Grade NAT) to provide shared IP addresses to customers, particularly in IPv4-scarce regions — so seeing an obviously private IP address on your WAN page is a sure sign your router is connected to the internet, but not with a separate, unique IP address.
5. Step-by-Step Fix
1-Ping your router’s own IP, then a public IP address directly
2-Restart your router and modem (with a full minute of downtime in between)
3-Check your router’s WAN page to see if it has a valid public IP address
4-Check other devices
5-Try using a different DNS
6-Check the status of your ISP
7-Test with an Ethernet cable plugged directly into your modem, if possible
6. Mesh WiFi Systems: A Different Set of Problems
If you’re on a mesh WiFi system (a set of two or more nodes connected together, one of which is connected to the modem), there’s a possibility of an issue unique to such systems — a failed backhaul connection between nodes. If a node is losing its connection to the main node (the one connected to the modem) while maintaining a strong local connection to your device, it’ll produce precisely these symptoms — the node has a strong WiFi connection, but no connection to the internet. Most mesh WiFi systems have a “network” or “topology” page that shows the status of the connection to the main node, so it’s a good idea to check if it shows as connected or not — if one of your satellite nodes has dropped its connection to the main node, that’s the issue.
7. Wrapping Up
DNS resolution issues are far more common than most people would expect when it comes to home networking, because a strong signal from your device to the router doesn’t necessarily imply that the router itself has a connection to the internet. Flushing your DNS and restarting your router covers the most likely possibilities in less than two minutes. If that doesn’t help, isolating the layer the problem is on using a few simple ping tests, followed by checking the WAN page on your router, should be enough to identify the cause in most cases. If you have a mesh WiFi system, the same applies, but with checking the status of the connection to the main node instead. If all else fails and there’s no obvious local cause, your ISP may have an outage on their end that prevents you from connecting to the internet.
8. FAQ
Why does my WiFi show full bars if there’s no actual connection?
The signal bars on your device only reflect the strength of your connection to the router — not whether the router has a connection to the internet.
Is this different from a slow connection?
It is, in that a slow connection still has data being transferred, albeit at a lower rate than expected. A failed connection attempt, on the other hand, means that no data is being transferred.
Can a VPN cause a speed test to show zero?
It can, if the VPN is failing to connect. Speed tests going through a VPN would show the speed of the VPN connection, not the actual connection speed. It’s a good idea to disable any VPN software you may have running before attempting a speed test.
What’s CGNAT and how do I know if it’s affecting me?
CGNAT stands for Carrier-Grade NAT, and it’s a method some ISPs use to give multiple customers the same IPv4 address. It affects everyone on that IPv4 address, and identifying it as the cause usually involves checking your router’s WAN status page to see if it has a public IP address or not.
Why would one room in my house lose internet connection on a mesh system?
That’s a characteristic of mesh systems — if the node in the room has lost its connection to the main node, it’ll stop working. It’s a good idea to check the status of the node in question using the application for your mesh system.
Should I test with a wired connection to rule out WiFi issues?
You should do that if the previous steps don’t help, as it rules out both your router and WiFi connection as possible causes. If you have a modem, try plugging your computer into it directly with an Ethernet cable — if that works, the problem is with your router or WiFi.
About This Guide
I’ve written this up after experiencing the issue on a mesh system, where one of the nodes would intermittently lose its connection to the main node, resulting in no internet connection for devices connected to it. Checking the status of the nodes in the mesh app revealed the issue, which wasn’t apparent from the local connection status.
More Related Fix:
https://appfixguide.net/wifi-keeps-disconnecting-how-to-fix-it-for-good/