ERR_TIMED_OUT means Chrome made a connection attempt to the server but gave up after waiting too long for a response. Unlike ERR_CONNECTION_TIMED_OUT (which happens at the TCP level), ERR_TIMED_OUT occurs when the connection is established but the server takes too long to respond with any data.
First, check if your internet is working and what your current IP address is:
🔍 Check My IP Address →The server is reachable but extremely slow — possibly overloaded, running a long database query, or throttling your connection. It can also be caused by slow DNS resolution, a VPN adding too much latency, or your network having packet loss that slows the connection enough to hit Chrome's timeout threshold.
Press F5 to reload. If you're on a slow connection, try first closing other bandwidth-heavy apps (streaming, downloads, backups). Run our speed test to confirm your connection is performing normally before assuming the server is the problem.
Open Command Prompt: ipconfig /flushdns. Clear Chrome cache: Ctrl+Shift+Delete → All time → Cached images → Clear. Also clear Chrome's DNS cache at chrome://net-internals/#dns.
VPNs add latency. If you're on a distant VPN server, the combined latency may push Chrome past its timeout threshold. Connect to a closer VPN server or disconnect entirely and test the direct connection.
Some extensions (particularly ad blockers or privacy tools) add processing time to each request. Test in incognito mode (Ctrl+Shift+N) where extensions don't run. If the page loads in incognito, find the slow extension at chrome://extensions.
Try accessing the site during off-peak hours (early morning vs. peak evening). If it loads sometimes but times out others, the server is genuinely overwhelmed at peak times. There's nothing you can do except try again later or contact the site owner.
✅ Fixed it? Visit tools.examineip.com to confirm your IP address and connection are working correctly.
← Back to the complete guide: Internet Errors Hub
Last updated: April 2, 2026 • Report an error