Why a website goes down for me but stays up for everyone else
You hit a website and it sits there spinning. A friend opens the same link and it loads fine. So is the site really down, or is the problem on your end?
Local problem or global problem
Before changing anything, find out whether the site is really down. If only you can not reach it, the cause is somewhere between your device and the wider internet. If it is down for many people, the cause is on the server side and you can not fix it from your end.
The fastest way to check is to open the QuickUptime checker, paste the link, and see what it says. Our tool runs a quick test from a server outside your network. If it reports the site as up, your problem is local.
Your DNS cache is stale
DNS is the system that turns a name like example.com into a number called an IP address. Your computer keeps a short list of recent lookups so it does not have to ask every time. That list is called the DNS cache.
If a website moved to a new server but your cache still points to the old one, the page will fail to load even though the site is fine. The fix is to clear the cache.
On Windows, open the Command Prompt and type ipconfig /flushdns. On a Mac, open Terminal and type sudo dscacheutil -flushcache then press return. On most phones, turning Wi Fi off and on, or restarting the phone, clears it.
You can also switch to a public DNS service such as Cloudflare at 1.1.1.1 or Google at 8.8.8.8. These services are usually faster and more reliable than the default DNS you get from your internet provider.
Your internet provider has a routing issue
Even when the public internet is working, your provider may have a bad route to one specific network. The route is the chain of hops that your traffic takes to get to the server.
If a hop in that chain is broken, the page will not load. Other sites still work because they take a different path. There is not much you can do as a normal user except wait a few minutes, switch to mobile data, or use a VPN that routes through a different network.
Tools like traceroute on Mac and Linux, or tracert on Windows, can show you where the path breaks. You do not need to read every line. If you see a long string of stars or timeouts at one hop, that hop is the problem.
Browser cache, cookies, or an extension
Browsers store copies of pages, images, and scripts to load them faster next time. That stored copy can get out of sync with the live site. Cookies, which are small bits of saved data, can also break things when the site updates how it expects them to look.
Try opening the page in a private or incognito window. Private windows ignore most of the saved data. If the site loads there, the cause is in your normal browser data and you can clear the cache and cookies for that site.
Browser extensions can also block parts of a page. Ad blockers, privacy tools, and script blockers sometimes block the wrong thing by accident. Turn extensions off and reload. If it works, turn them on one at a time to find the culprit.
A firewall, VPN, or DNS filter is blocking it
Your home router, work network, school network, or a public Wi Fi spot may block certain sites. Parental control apps, antivirus tools, and corporate filters can also block addresses they consider risky.
If you are on a VPN, the VPN provider may also be blocked by the site, or the VPN itself may be blocking outbound traffic. Try turning the VPN off and reloading. If the page works without the VPN, you have your answer.
A quick test is to switch from Wi Fi to your phone's mobile data and try again. If the site loads on mobile data but not on Wi Fi, the block is somewhere in the Wi Fi network you were using.
Your device clock is wrong
This one surprises a lot of people. Modern websites use HTTPS, which depends on certificates that are valid only for a specific date range. If your device clock is far off, the browser thinks the certificate is not yet valid or has expired, and it refuses to load the page.
Open your device's date and time settings and make sure it is set to update automatically. If the time is way off, fix it, then reload the page.
A quick fix checklist
When a site loads for others but not for you, run through this in order:
- Check on QuickUptime to see if the site is really up.
- Try the page in a private or incognito window.
- Switch from Wi Fi to mobile data.
- Flush your DNS cache and try again.
- Turn extensions off, especially ad blockers.
- Check that your device clock is accurate.
- Restart your router if you have access to it.
If none of those help, the problem may be a regional outage with your internet provider or a route issue between your network and the site. Wait fifteen to thirty minutes and try again. Most of these clear up on their own.