Quick Answer: ERR_TIMED_OUT means Chrome sent a request to a website but never got a response back in time. It’s usually a slow or congested Wi-Fi connection, a VPN or proxy extension slowing the request, or a server that’s genuinely overloaded. Restarting your router and disabling VPN extensions clears most cases.
What Causes This Error
- Slow or congested Wi-Fi network struggling to complete the request
- A VPN or proxy extension intercepting and delaying traffic
- A firewall or content filter silently dropping the request instead of blocking it outright
- DNS resolving the site correctly, but the server itself failing to respond
- The website itself being overloaded or temporarily down
How to Fix It
Step 1: Reload the page
A single dropped packet can trigger this error even on a healthy connection. Press Ctrl + R and see if it loads normally the second time.
Step 2: Test a different site
Try a well-known site like google.com. If it loads fine, the problem is specific to the original site, not your connection.
Step 3: Restart your router
Unplug it for 30 seconds. Congested or overheated routers frequently cause exactly this symptom — requests going out but never completing.
Step 4: Disable VPN and proxy extensions
Go to chrome://extensions and turn off any VPN, proxy, or ad-blocking extension one at a time. These reroute your traffic and are a common source of timeouts, especially on free or overloaded VPN servers.
Step 5: Switch to a public DNS server
Go to Settings > Network > Wi-Fi > (your network) > Network > Name servers and switch to Google (8.8.8.8) or Cloudflare (1.1.1.1). A slow ISP DNS server can add enough delay to trigger timeouts on some sites.
Step 6: Try a different network
Connect to a phone hotspot briefly. If the site loads instantly there, the issue is with your home network or ISP, not the Chromebook itself.
Still Not Fixed?
If ERR_TIMED_OUT follows a single site across every network you try, that site is very likely down or blocking your region/IP range. If it happens across every site on every network, an ISP-level routing issue is the most likely cause — contact your provider.
FAQ
Is ERR_TIMED_OUT the same as the site being down?
Not necessarily. It means no response arrived in time, which can be caused by your connection, a firewall, or the site itself. Testing on a different network narrows this down quickly.
Does a VPN really cause this?
Yes, frequently. Free or overloaded VPN servers add latency that can push a normal request past Chrome’s timeout threshold.
Does this mean something is wrong with my Chromebook?
Rarely. This is almost always a network-path issue rather than a device fault, which is why testing a different network is the fastest way to isolate the cause.
