ERR_NETWORK_CHANGED means Chrome gave up on a page because your network changed while the page was still loading. On a Chromebook, the usual cause is the device quietly hopping between two saved Wi-Fi networks. If the error keeps coming back, open Settings, Network, Wi-Fi, Known networks, and forget every network you do not actually use in that room.
Applies to
- Devices: Chromebooks and Chromeboxes running ChromeOS. The same error appears in Chrome on Windows, Mac, and Android, and most of this page applies there too.
- Settings names: match the current ChromeOS Settings app as documented by Google in July 2026.
- Account: none needed. This is a network error, not a sign-in error.
- Difficulty: easy. Nothing here needs developer mode, a Powerwash, or the command line.
What does ERR_NETWORK_CHANGED actually mean?
Chrome shows this page when the network path underneath a request changes in the middle of that request. The address you were loading was fine. The connection was fine. Then the device switched networks, picked up a new IP address, or lost and regained its link, and Chrome threw away the half-finished request rather than finish it over a different path.
There is a detail here that most pages about this error miss, and it changes what you should do. In Chromium’s own list of network errors, this one is NET_ERROR(NETWORK_CHANGED, -21), and it lives in the block of codes numbered 0 to 99, which the file labels as system related errors. It sits directly beside BLOCKED_BY_CLIENT at -20. Real connection failures like ERR_CONNECTION_REFUSED and ERR_CONNECTION_TIMED_OUT live in a different block, numbered 100 to 199.
In plain words: -21 is Chrome cancelling its own request, not a server or a website refusing you. That is why the standard advice you see everywhere, flush your DNS and reset your router, so often does nothing. It is aimed at a layer that never failed.
Is one ERR_NETWORK_CHANGED a problem?
No. If you just woke your Chromebook, walked between two rooms, unplugged an Ethernet adapter, joined a different network on purpose, or turned a VPN on or off, one of these errors is normal and correct. Press Reload and the page will load over the new path.
It is only worth investigating when it repeats on its own while you sit still, which is exactly what people describe in the Google Chrome Community thread Frequent ERR_NETWORK_CHANGED errors and in the older thread I keep getting ERR_NETWORK_CHANGED when trying to access websites. Chromebook owners describe the matching symptom from the other side in the Chromebook Community thread Why does my Chromebook keep switching to a different Wi-Fi. Same event, two descriptions.
Why it keeps happening on a Chromebook
There are four causes worth your time. Each one has a signal that tells you it is yours, so you do not have to try all of them.
- Two saved networks are competing. Signal: the Wi-Fi name in the bottom right status area is not always the same one, or you have both a 2.4 GHz and a 5 GHz name saved for the same router, or a neighbour’s open network and a guest network are saved.
- A Passpoint subscription is pulling you onto a partner network. Signal: you never chose the network you are on, and you have an Android carrier or Wi-Fi app installed. ChromeOS connects to Passpoint networks automatically, with no prompt.
- Your phone’s hotspot is taking over. Signal: it happens when your phone is nearby, and you have Instant tethering set up under Connected devices.
- The link itself keeps dropping and returning. Signal: the network name never changes, but the signal icon dips, and other devices in the same room also stumble. A drop and recovery counts as a network change too.
The 60-second diagnosis
Do this before you change any setting. It tells you which branch above is yours.
- Watch the network name. Trigger the error, then look at the bottom right of the shelf and note the Wi-Fi name. Do it again the next time it happens. A different name means you are switching networks. The same name means your link is dropping instead.
- Count your saved networks. Open Settings, select Network on the left, then Wi-Fi, then Known networks. If that list has more than the networks you actually use where you sit, you have found your likely cause.
- Check for Passpoint. On the same Known networks screen, look for a Passpoint subscriptions section. Anything listed there can connect your Chromebook without asking.
- Check tethering. Open Settings, then Connected devices, select your phone, and see whether Instant tethering is on.
If two saved networks are competing
This is the common Chromebook case, and it is the one that produces a repeating loop rather than a single error. Fix it in this order.
Before you start: forgetting a network deletes its saved password from this Chromebook. Make sure you know the password before you remove a network you still need.
- Forget the networks you do not use. Go to Settings, Network, Wi-Fi, Known networks. Next to a network name, select More, then Forget. Clear out old cafes, guest networks, and any open network you joined once.
- Pick a winner. Go to Settings, Network, Wi-Fi, then select the network you want to stay on, and turn on Prefer this network. This tells ChromeOS which one to choose when more than one is in range.
- Stop the loser from auto-joining. Select the other network and turn off Automatically connect to this network. Leaving both networks preferred and automatic is what lets the device flap between them.
- Deal with split band names. If your router advertises separate names for its 2.4 GHz and 5 GHz bands, keep the one that is reliable where you sit and forget the other on this Chromebook.
If a Passpoint subscription is switching you
Passpoint is a ChromeOS feature that connects you to a provider’s partner networks automatically, using credentials installed by an Android app. It is genuinely useful in a city, and genuinely annoying at a desk that sits within reach of a partner hotspot, because you can be moved onto a weaker network without a prompt.
- Open Settings, Network, Wi-Fi, Known networks.
- Under Passpoint subscriptions, select a subscription to see which networks and provider domains it covers.
- To stop it, select More next to the subscription and choose Remove. Uninstalling the Android app that installed it does the same thing.
Note that Passpoint subscriptions are per device and are not synced across your Chromebooks, so a Chromebook that misbehaves while another one is fine is a good hint that you should look here.
If your phone’s hotspot is taking over
Instant tethering lets a Chromebook connect to your Android phone’s mobile data by itself. Handy on a train, and a source of mid-page network changes at home. Open Settings, then Connected devices, select your phone, and turn Instant tethering off. Your phone’s hotspot will still be available manually under Your device hotspots in the network menu when you actually want it.
If the link keeps dropping instead
Use this branch when the network name never changes. A drop and a reconnect looks identical to a switch as far as Chrome is concerned.
- Move closer to the router, or move the Chromebook off a metal shelf or away from a microwave, and see whether the error stops.
- Restart your router. Unplug it, wait 30 seconds, plug it back in.
- Update ChromeOS. Go to Settings, About ChromeOS, and select Check for updates. Wi-Fi driver fixes ship in ChromeOS updates.
- Turn off any VPN and test again. A VPN that reconnects on its own changes the network path and can produce this error on a perfectly healthy Wi-Fi network.
- Compare with another device. If a phone on the same network stumbles at the same moments, the problem is the network, not the Chromebook.
How it compares to other Chrome network errors
Chrome uses a different code for each kind of failure. Knowing which one you have tells you which layer to look at.
| Error | Chromium code | What happened |
|---|---|---|
| ERR_NETWORK_CHANGED | -21 | Chrome cancelled the request because the network path changed under it |
| ERR_INTERNET_DISCONNECTED | -106 | No network at all when the request started |
| ERR_CONNECTION_RESET | -101 | The connection opened, then was dropped |
| ERR_CONNECTION_TIMED_OUT | -118 | No reply arrived in time |
| ERR_NAME_NOT_RESOLVED | -105 | The address could not be turned into an IP |
The pattern is worth remembering. Only the first one is Chrome stopping itself. The rest are things that happened out on the network, which is why they respond to router, DNS, and firewall fixes and this one usually does not.
What we could not verify
We could not find any official Google acknowledgement of a ChromeOS bug that causes ERR_NETWORK_CHANGED to repeat, and no Chromium issue that describes it as a defect rather than expected behaviour. Everything above is drawn from Chromium’s published error list, Google’s own ChromeOS network documentation, and user reports. If a fix on this page does not help, that is worth saying plainly rather than guessing at a cause: the honest answer is that your device is reporting a real network change, and the work is finding what keeps changing it.
FAQ
Is ERR_NETWORK_CHANGED caused by the website?
No. It is generated on your device. Chrome cancels its own request when the network underneath changes mid-load, so the site never gets a chance to fail. If a single site is failing and others load, you are looking at a different error.
Why does it only happen on my Chromebook and not my phone?
Usually because the Chromebook has more saved networks, a Passpoint subscription, or Instant tethering set up, and your phone does not. Passpoint subscriptions in particular are stored per device and are not synced, so two Chromebooks on the same account can behave differently.
Should I flush DNS or reset my network settings?
Not first. This error is not a name lookup failure, so a DNS flush rarely changes anything. Clean up your known networks and check Passpoint and tethering before you reset anything, since a full reset also deletes every saved Wi-Fi password.
Can a VPN cause ERR_NETWORK_CHANGED?
Yes. A VPN connecting, dropping, or switching servers changes the network path, which is exactly the condition this error reports. Turning the VPN off for a few minutes is a fast way to rule it in or out.
Bottom line
ERR_NETWORK_CHANGED is a report, not a fault. One of them after you move or wake your Chromebook is normal. A repeating one means something keeps changing your network, and on ChromeOS that something is usually a second saved network, a Passpoint subscription, or your phone’s hotspot. Watch the network name during the error, then fix only the branch that matches.