The ERR_NETWORK_CHANGED error in Google Chrome is a network-level interruption that often appears when an Accelerated Mobile Pages (AMP) document fails to load. Unlike generic connection errors, this one specifically signals that the browser detected a change in the network state—such as a switch from Wi‑Fi to cellular, a VPN reconnect, or a proxy timeout—while the page was being fetched. For developers building AMP pages, this error is a common headache—AMP’s pre-rendering and caching mechanisms make the browser extra sensitive to network transitions.
When Chrome attempts to load an AMP page, it often pre-renders the document in the background to deliver near-instant load times. If the network changes during that pre-render phase, Chrome cancels the initial request and throws ERR_NETWORK_CHANGED. The user sees a blank or broken page, even though the underlying network later stabilises. This behaviour is by design—Chrome prioritises security and consistency over showing stale or partially loaded content.
What Triggers ERR_NETWORK_CHANGED in AMP?
The error isn’t unique to AMP, but AMP’s architecture makes it more likely. Common triggers include:
- Network interface flapping: Rapid switching between Wi‑Fi, Ethernet, or mobile data. For example, a laptop waking from sleep while connected to both Wi‑Fi and a tethered phone.
- VPN or proxy reconnections: Corporate VPNs that drop and reconnect, or browser proxy extensions that change routing mid‑request.
- DNS resolution changes: When the operating system’s DNS server changes (for example, after connecting to a new Wi‑Fi network with a different DHCP lease).
- Browser extension interference: Extensions that modify network requests—ad blockers, privacy tools, or bandwidth limiters—can cause Chrome to detect a network change even when the physical link is stable.
- Server-side redirects with cache-busting: AMP caches (like Google’s AMP Cache) may redirect to a canonical URL, and if the redirect triggers a new network path, Chrome may interpret it as a change.
In a development environment, you might also see this error when testing local AMP pages with a self-signed certificate—Chrome treats certificate validation failures as a network change.
How to Diagnose the Error
Before applying fixes, confirm the error is indeed ERR_NETWORK_CHANGED and not another network issue. Open Chrome’s Developer Tools (F12), go to the Network tab, and reload the page. Look for requests that were cancelled (status “(cancelled)”). The timing column will show if the request was aborted due to a network change. Also check the Console tab for related messages like “Fetch failed loading: ERR_NETWORK_CHANGED”.
If the error appears only on AMP pages and not on regular HTML pages, the problem is likely AMP-specific. If it appears on every page, the root cause is a broader network issue.
Practical Fixes for Developers and Users
1. Stabilise Your Network Connection
For developers testing locally, avoid using Wi‑Fi with weak signal or switching between networks. Use a wired Ethernet connection when running AMP validation tools. If you must use Wi‑Fi, disable power-saving features that may temporarily drop the interface. On Linux, you can check interface stability with watch -n 1 cat /proc/net/dev to see if packet counts pause unexpectedly.
2. Disable or Configure VPNs and Proxies
Corporate VPNs often use split tunneling. If the VPN renegotiates keys during an AMP pre-render, Chrome sees a network change. For development, set your VPN to allow direct access to localhost and avoid routing AMP cache domains through the tunnel. On macOS, you can configure exceptions in the Network settings. On Linux, use ip route to add specific routes bypassing the VPN for AMP cache IP ranges (e.g., 172.217.0.0/16).
3. Clear the AMP Cache
Chrome caches AMP documents aggressively. A corrupted cache entry can cause repeated ERR_NETWORK_CHANGED errors. Clear the cache for the specific site: open DevTools → Application → Clear storage → Clear site data. Alternatively, use chrome://settings/clearBrowserData and select “Cached images and files” for the past hour.
4. Check Browser Extensions
Extensions that block scripts or modify headers (e.g., uBlock Origin, Privacy Badger) can interfere with AMP’s pre-render. Temporarily disable all extensions and test the AMP page. If the error disappears, re‑enable extensions one by one to find the culprit. For your own development, consider using a separate Chrome profile without extensions for AMP testing.
5. Adjust Chrome Flags (Advanced)
Chrome has experimental flags related to network prediction and pre-rendering. These can be toggled to reduce false network-change detections. Navigate to chrome://flags and set:
- #enable-prerender2 to “Disabled” – disables the new pre-rendering engine that may be more sensitive to network changes.
- #network-service to “Disabled” – forces Chrome to use the old network stack (less aggressive about detecting changes).
These flags are experimental; they may affect other browsing behaviour. Revert them after testing if they cause issues.
6. Validate Your AMP HTML
If you are building an AMP page and the error occurs for visitors, your AMP markup might be triggering unexpected redirects. Use the C Programming for Beginners approach of checking every external resource—use the AMP validator () to ensure all scripts and images are correctly referenced. Incorrect amp-script or amp-iframe usage can cause the AMP runtime to abort loading, which Chrome may misinterpret as a network change.
7. Use a Reliable DNS Provider
DNS flapping can cause Chrome to think the network changed. Set your system to use a stable DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8). On Linux, edit /etc/resolv.conf or use NetworkManager settings. On Windows, change IPv4 DNS in adapter properties. A consistent DNS reduces the chance of Chrome aborting AMP pre-renders.
When the Error Is a Symptom of a Larger Issue
If you are seeing ERR_NETWORK_CHANGED frequently across multiple sites and browsers, your network hardware may be failing. Faulty routers, loose Ethernet cables, or ISP throttling can cause intermittent drops that Chrome detects. Run a continuous ping to a stable host (e.g., ping -t 8.8.8.8 on Windows, ping 8.8.8.8 on Linux/macOS) and watch for timeouts. If you see packet loss, the problem is at the infrastructure level, not Chrome.
For developers managing AMP pages on a server, check your server logs for incomplete requests. A misconfigured CDN or load balancer that closes connections prematurely can trigger Chrome’s network-change detection. Ensure your server sends proper Connection: keep-alive headers and does not terminate idle connections too aggressively.
Using Diagnostic Tools in a Lab Environment
To safely reproduce and study ERR_NETWORK_CHANGED without affecting production, set up a local AMP test lab. Tools like Wireshark or tcpdump can capture packets during the error. On Linux, you can simulate network changes using nmcli to disable and re-enable the interface while an AMP page is loading. This is a controlled way to see exactly which TCP handshake fails. For a broader understanding of network diagnostics, you might find the techniques discussed in the Best Linux Music Player Apps article useful—though that focuses on audio, the underlying system monitoring commands (like journalctl) apply to network debugging as well.
Final Actionable Step
If you encounter ERR_NETWORK_CHANGED on a specific AMP page you are developing, start by disabling all browser extensions and clearing the AMP cache. Then reload the page with Chrome DevTools open on the Network tab. If the error persists, use a second device on the same network to load the same AMP URL—if it works there, the problem is local to your first device’s network stack. In that case, check your VPN configuration and DNS settings. For a permanent fix on your development machine, create a dedicated Chrome profile with flags tuned for AMP testing, and keep your network interface physically stable during validation runs.
