Website Down for Some Visitors but Not Others
The site loads fine on your screen, but a customer swears it is down — and you cannot fix, or even see, what they are seeing.
Common signs of this issue
- A customer or colleague reports the site is down while it loads normally for you.
- The complaints cluster: one office, one town, one country, one mobile carrier, or "everyone on their phones."
- It started within a day or two of a domain, DNS, or hosting change.
- Affected people see different errors: some get "site can't be reached," others a security warning, others an old version of the site.
- The same person finds the site works on wifi but not mobile data, or the other way around.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Ask every affected person for a screenshot of the exact error. This is the highest-value step: "can't be reached," "timed out," "refused to connect," and a certificate warning all point at different causes — "it's down" tells you nothing.
- Ask two more questions: are they on wifi or mobile data, and roughly where are they? Failures that follow a network type or a geography are the signature of DNS, IPv6, or regional problems.
- Have one affected person switch networks — wifi off, mobile data on, or the reverse. If the site appears, their original network holds a stale address or blocks the site; your server is fine.
- Search for a free "DNS propagation checker" and enter your domain — it shows what address different parts of the world get, and mixed answers mean the internet's address book is still updating. Pair it with a free uptime-checker site that tests your site from multiple locations at once; between them you learn whether the outage is real, partial, and roughly where it lives.
- Ask yourself what changed in the last 48 hours: a domain transfer, new nameservers, a hosting move, a new CDN or Cloudflare setup. If yes, patchy availability for up to a day or two is normal and usually heals itself.
- If the affected people are mostly on phones, ask your host whether your IPv6 records are correct. Sites are reachable at two kinds of addresses — older IPv4 and newer IPv6 — and a wrong IPv6 entry breaks the site only for networks that prefer it: a classic "some mobile users can't see it" cause.
- Trust outside checkers over your own computer. You visit your site constantly, so your machine caches its address longer than anyone's — your screen is the least reliable witness in the room.
What this usually means
A website that is down for some people and up for others is almost never half-broken. What differs is the path each visitor takes to reach it: which copy of the internet's address book their network consulted, which addressing system they travel over, which regional data center serves them, and what their own network allows through. The site sits in one place; the routes to it fail unevenly.
The most common cause by far is DNS propagation after a recent change. When you move hosts or edit domain settings, the new address does not reach the whole internet at once — every network keeps a cached copy of the old answer and refreshes it on its own schedule, which can take up to 48 hours. During that window, visitors whose networks refreshed early reach the new server while everyone else is sent to the old address. The same patchiness can appear without any change on your part when one internet provider's DNS holds a stale or broken cache.
When no DNS change explains it, the remaining suspects each have a signature. A wrong IPv6 record breaks the site only for networks that prefer the newer addressing — often mobile carriers. A CDN or Cloudflare issue at one data center breaks one region while the rest of the world is fine. An office firewall or country-level blocking stops one specific group, and your own server's security may have banned certain visitor addresses it mistook for attackers.
What not to do
- Don't declare the site fine because it loads for you — your own computer is the least reliable witness available.
- Don't make another round of DNS changes to hurry propagation along. Each change restarts the waiting period and makes the patchiness last longer.
- Don't rebuild pages, reinstall the site, or restore backups — if some visitors reach the site normally, the site itself is intact.
- Don't dismiss reports as the visitor's computer acting up. A pattern of reports from one region or network is real data.
- Don't switch hosting companies mid-propagation. Moving again while the address book is still settling produces days of confusion instead of hours.
- Don't make cache-flushing on visitors' devices your main strategy. It may help one person, but it fixes nothing for the silent others hitting the same wall.
When to get help
If a propagation checker still shows wrong or mixed addresses more than 48 hours after your last change, stop waiting — something in the DNS setup is actually wrong, and it is exactly the kind of fiddly, high-consequence configuration a professional untangles in under an hour while trial and error stretches across days of partial outage. The same goes when the pattern points at IPv6 or a server-side ban list: confirming those takes tools and access most owners do not have, while some slice of your customers quietly cannot reach you. What you can do better than anyone is collect the evidence — screenshots, locations, wifi versus mobile data — that pattern is most of the diagnosis, and handing it over turns an open-ended investigation into a short one.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
Why does my website work for me but not for others?
Different visitors take different paths to your server. Their networks may hold an outdated cached address after a recent change, prefer a broken IPv6 route, be served by a struggling regional data center, or be blocked by a firewall or the server's own security. The site is usually intact — some routes to it are failing.
How long does DNS propagation take?
Most of the internet picks up a change within a few hours, but stragglers can take 24 to 48 hours because every network refreshes its cached copy on its own schedule. If mixed results persist beyond 48 hours, stop waiting — something in the DNS setup is genuinely wrong.
How can I check if my site is really down for other people?
Use a free uptime-checker site that tests from multiple locations worldwide, plus a DNS propagation checker to see what address different regions get for your domain. Together they show whether the outage is real, partial, and roughly where it lives.
Why can some mobile users not see my website?
Mobile carriers often prefer the newer IPv6 addressing system. If your domain's IPv6 record is wrong or points somewhere dead, the site breaks only for networks using it — phone users fail while desktop users are fine. Your host can verify the record.
Can my own server block some visitors from my site?
Yes. Server security software can automatically ban visitor addresses it mistakes for attackers — commonly after repeated failed logins from an office sharing one address. Those visitors are locked out while everyone else browses normally; your host can check and clear the ban list.