Status and Reliability

Website is down for me but not for others

Separate local network problems from real outages by checking status, DNS, SSL, redirects, and edge provider behavior.

Run Status Checker Browse workflows

Workflow shape

1Confirm the symptom

2Collect live evidence

3Fix in the right order

4Retest the same URL

What this means

A partial outage can come from DNS propagation, regional CDN issues, local resolver cache, SSL hostname gaps, firewall rules, or redirect loops that only affect certain clients.

Use this when

Some users can open the site while others cannot.
The site fails on one network, country, or device.
You recently changed DNS, CDN, SSL, hosting, or redirects.

Evidence

What to collect before changing anything

The affected URL, location, network, browser, and exact error message.
HTTP status, response time, and redirect chain.
A, AAAA, CNAME, NS, and TTL values from public resolvers.
Certificate hostname coverage and expiry status.

Diagnosis

Run the checks in this order

1Run Status Checker for the exact domain or URL.
2Run DNS Lookup and DNS Propagation Checker if DNS changed recently.
3Run SSL Certificate Checker if the browser shows a privacy or certificate warning.
4Run Redirect Checker when the browser spins or lands on the wrong host.
5Compare failing and working networks before changing production settings.

Fix plan

What to fix first

1Fix DNS records and wait for TTL windows when propagation is the issue.
2Correct SSL hostnames or CDN certificate settings if HTTPS fails only for certain hosts.
3Remove redirect loops and normalize apex or www routing.
4Check firewall, WAF, or bot-protection rules if only a region or ISP is blocked.
5Document the incident with timestamps and test evidence.

Retest

How to confirm the fix worked

Re-run status, DNS, SSL, and redirect checks after each change.
Test on at least two networks or public resolvers.
Confirm monitoring reports recovery before closing the incident.

FAQ

Common questions

Why can my site be down only for some people?+

DNS, CDN, SSL, firewall, and resolver caches can differ by network or region. A partial failure is common after infrastructure changes.

Should I change DNS again immediately?+

Not until you know the failing layer. Repeated DNS changes can extend confusion and make evidence harder to interpret.

Loading CheckWebs…