It's 11:58 p.m. The form is due at midnight. You hit Submit and get a gray "This site can't be reached" page.
You refresh. You refresh harder. You restart the router, which eats four minutes you don't have. You start to wonder whether the whole internet has fallen over.
It probably hasn't. When a website won't load, it's usually one of three things: the site is down, something between you and the site is blocking it, or something on your device or network is broken. From your couch, all three look identical. They're not, and each one has a different fix.

What Happens When a Page Loads
Loading a website feels instant, but a typical page load goes through four distinct stages. They tend to fail in different ways, which means your browser's error message is usually a diagnostic clue.
| Step | What happens | What it looks like when it breaks |
|---|---|---|
| 1. Name lookup (DNS) | Your device asks a DNS server for the site's numerical IP address. | Server IP address could not be found or DNS_PROBE_FINISHED_NXDOMAIN |
| 2. Connection | Your device connects to the returned IP address (a server, load balancer, or CDN). | ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED |
| 3. Secure handshake | Your browser and the site negotiate encryption and check SSL certificates. | Certificate warnings, handshake failures, or connection resets |
| 4. The site's answer | The server responds with the webpage or an HTTP status code. | HTTP errors like 403, 404, 429, or 500–504 |
Step 1: Find Out If It's Down for Everyone
Before changing local settings, confirm whether the outage is on your end at all.
- Check an independent status site: Use crowd-sourced tools like Downdetector or a multi-region URL checker to see if other users are reporting issues.
- Check the site's official status page: Major services (like AWS, GitHub, or Cloudflare) publish real-time status dashboards linked from their footers or support portals.
- Look at social media: When major platforms drop offline, user reports spike quickly on public forums.
Step 2: Rule Out Your Device
If the site is reachable for everyone else, the issue resides between your screen and the target server.
- Try another browser: If the page loads in Firefox but not Chrome, the issue is tied to your primary browser's cache, cookies, or extensions.
- Perform a hard refresh: Bypass saved cache files using
Ctrl+F5(Windows) orCmd+Shift+R(Mac). - Open an Incognito/Private window: This disables cookies and most browser extensions. If it loads, turn extensions back on one by one to find the culprit.
- Check another device on the same Wi-Fi: If your phone loads the site over Wi-Fi but your laptop doesn't, the issue is isolated to your laptop.
- Verify system date and time: An incorrect system clock will break SSL certificate validation, triggering secure connection errors across multiple sites.
Step 3: Rule Out Your Network
If your hardware and browser check out, inspect the network path.
Try Mobile Data
Disable Wi-Fi on your mobile phone and load the page over cellular data. If it opens on mobile data, the failure is localized to your home Wi-Fi network, local DNS resolver, or ISP.
Check for Captive Portals
Public Wi-Fi networks (hotels, airports, cafes) hold traffic back until you accept their terms. Secure HTTPS sites will fail or throw certificate errors until you complete the captive portal sign-in.
Test Your DNS Resolver
DNS servers map web addresses to IP addresses. If your DNS server fails, healthy websites become unreachable. Test this via Command Prompt (Windows) or Terminal (macOS/Linux):
- Run
nslookup example.com(queries your default DNS). - Run
nslookup example.com 1.1.1.1(queries Cloudflare's public DNS).
| Result | What it means |
|---|---|
| Both return IP addresses | Your DNS is working normally. The issue lies in the server connection or application layer. |
Your default DNS fails; 1.1.1.1 succeeds |
Your ISP or router's default DNS server is down or filtering that domain. |
| Both requests fail | The domain's DNS is misconfigured, or your local network is blocking outbound DNS traffic. |
If your DNS looks like the problem, clear your DNS cache first. If that doesn't help, consider switching to a reputable public resolver whose privacy policy you trust. Control D's free DNS is one option.
Restart Your Router
The oldest trick in IT, and still worth a try. Unplug the router (and the modem too, if it's a separate box), wait about 30 seconds, then plug it back in. It can clear stale local settings and start a fresh connection with your ISP.
Down or Blocked? How Network Blocks Show Up
Sometimes "down" actually means "blocked". ISPs, corporate networks, and websites themselves enforce blocks using distinct methods:
| Block Type | How It Behaves | Primary Clue |
|---|---|---|
| DNS Filtering (Schools, Workplaces, ISPs) | Displays "Server not found" or redirects to a landing page. | Loads normally if you switch to a custom DNS server. |
| IP Blocking (ISPs, Governments) | Connection times out completely. | Fails across all DNS resolvers, but loads through an encrypted VPN tunnel. |
| SNI / Handshake Filtering (Restrictive Networks) | Connection drops or hangs during the TLS handshake. | Standard HTTP sites work, but specific secure HTTPS addresses stall out. |
| Geo-Blocking (Content Hosts) | Displays HTTP 403 or 451 ("Unavailable in your region"). |
Site loads, but actively refuses access based on your IP location. |
| VPN / Datacenter Blocking (Services) | Displays 403 Forbidden, CAPTCHA loops, or access denied. |
Fails while connected to a VPN, but loads immediately when disconnected. |
When a Site Only Breaks on Your VPN
Works fine with the VPN off, falls apart the moment you connect? It's one of the most common questions any VPN gets, and it usually comes down to two things.
The Site Blocks VPN IPs
Many VPN locations use IP addresses shared by multiple users, often from datacenter ranges. Some sites treat that as suspicious and may respond with 403 errors, CAPTCHA loops, or an access-denied page.
- Try another location first. Changing locations usually gives you a different shared IP, and sites block IPs independently. If one IP is blocked, another location may work. With Windscribe, you can choose from servers in 69+ countries and 135+ cities.
- Clear the site's cookies after connecting. Cookies from your real location can clash with your VPN location, which can look suspicious to the site.
- Rotate your IP. On our paid plans and locations, you can set up IP Rotation, which requests a different IP without you having to disconnect.
- Consider a Static IP. A Static IP (we offer it as an add-on on your Pro plan) gives you the same shared IP, usually with fewer than 10 people on it, whenever you connect to that Static IP location. That may improve access with some services. It's a separate purchase, and it's not a guarantee.
A Filter Is Catching It
R.O.B.E.R.T., our DNS-level blocker, works in the Windscribe apps and supported custom configs. Blocklists are great until one catches a domain a site needs to load. If you get a DNS-style "site not found" error only when you're connected, it could be R.O.B.E.R.T., rather than the site being down.
Quick test: Turn off the blocklist you suspect (Ads + Trackers is a common one) and reload. If the site works, turn the list back on and allow just that domain in My Account > Security > Custom Rules, with Action set to Allow. Free accounts get up to three custom rules.
Use Split Tunneling as a Test
Split Tunneling lets chosen apps skip the VPN. Some desktop apps also support excluding IPs and hostnames. On Android, use app-based Split Tunneling where supported. Exclude the site (on desktop) or your browser app, then reload. If the site works outside the tunnel, that strongly suggests the VPN path or the VPN's IP is involved.
Two things, though. Excluded traffic uses your real IP, so only exclude what you're comfortable exposing. And on desktop, excluding an app doesn't bypass R.O.B.E.R.T., so a R.O.B.E.R.T. block needs a Custom Rule, not a split tunnel.
Our Own Catch
Fair's fair. Here's where a VPN, including ours, won't save you:
- It can't fix a site that's down. Switching VPN locations won't bring back a site whose own servers, or the services it depends on, are down.
- It can't promise access past every block. Some networks block VPNs too. Our anti-censorship settings give the app extra ways to connect, but no VPN can guarantee access on every restrictive network.
- It can't make every site accept VPN IPs. Some sites block shared IPs on purpose.
- It can't fix your Wi-Fi. If the problem is your router, it's still your router.
When It's Actually Down
Sometimes it really isn't you. Then the plan is short:
- Wait, then check again. Many outages clear up without you doing anything.
- Watch the status page or the company's official social accounts for updates.
- Don't reinstall anything. If the site is down, clearing cookies or reinstalling your browser won't help, and you'll just be logged out when it comes back.
- Need something from a public page? The Internet Archive's Wayback Machine may have a saved copy.
Be Smart
When a website won't load, resist the urge to restart everything you own. Go in order: check if it's down for everyone, rule out your browser, test your local Wi-Fi against mobile data, check your DNS, and then test your VPN connection. Working from the outside in isolates the failure in minutes so you can apply the exact fix instead of guessing.
Frequently Asked Questions
Why does a website load on my phone but not my computer?
If both devices are on the same Wi-Fi network, the issue is isolated to your computer. This is typically caused by stale browser cache, an aggressive browser extension, misconfigured DNS settings, or background security software like a firewall. If your phone is using cellular data instead, the issue lies further up your home network path. Put both devices on the exact same network to verify.
Why does a website work on mobile data but fail on Wi-Fi?
This outcome isolates the problem to your home Wi-Fi network path. The culprit is usually your router, your ISP's default DNS server, parental control filters, or an ISP-level domain block. Cellular data uses an entirely separate network, IP pool, and DNS infrastructure. To fix it, try restarting your router, clearing your local DNS cache, or switching to a public DNS resolver.
Can my ISP block specific websites?
Yes, ISPs routinely restrict access to specific websites, often to comply with local regulations, copyright orders, or government censorship. They typically enforce these blocks using DNS filtering, IP address blocking, or inspection during the secure TLS handshake.
What does ERR_CONNECTION_RESET mean?
This error indicates that the connection between your browser and the remote server was forcibly closed before the page payload finished loading. It can stem from a temporary server crash, network instability, or local antivirus software interfering with the connection. On restricted networks, it is also a common symptom of a firewall actively dropping your connection during the secure handshake.
Why do I get CAPTCHAs or 403 errors when using a VPN?
Websites frequently block or flag commercial datacenter IP ranges to stop automated bots and credential stuffing attacks. Because hundreds of VPN users may share a single server IP, security systems like Cloudflare view that traffic as suspicious. Clearing your browser cookies and switching to a different VPN server or a Static/Residential IP usually solves the problem.
Can clearing my browser cache actually fix a website that won't load?
Yes. Browsers store copies of website files (like scripts and stylesheets) to speed up load times, but if a site updates its code or if local files get corrupted, your browser may keep trying to load broken, outdated data. Performing a hard refresh (Ctrl+F5 or Cmd+Shift+R) forces the browser to discard stored files and request a fresh copy directly from the web server.
How do I know if a website is blocked by DNS or by IP?
You can test this by running a quick DNS lookup in your command terminal using a public DNS address like nslookup site.com 1.1.1.1. If changing your DNS resolver gives you a valid IP and the site opens, it was a DNS block. If the request times out regardless of which DNS server you use, the network is blocking the site's IP address directly.