Is It Down for Everyone, or Just You?§

There are few digital experiences more frustrating than trying to access a crucial website — whether it is your online banking portal, an essential cloud SaaS tool, a client's e-commerce shop, or your favorite social network — only to be greeted by an indefinite loading spinner or an abrupt browser error screen:

  • DNS_PROBE_FINISHED_NXDOMAIN
  • ERR_CONNECTION_REFUSED
  • 502 Bad Gateway
  • 504 Gateway Timeout

When this happens, your first critical question is always: Is the entire service down globally, or is the problem localized to my device, Wi-Fi router, local ISP, or DNS resolver?

In this comprehensive guide, we will walk you through the architecture of website outages, how to pinpoint whether a failure is server-side or client-side, the technical meaning of HTTP status codes and DNS records, and actionable step-by-step troubleshooting techniques you can use right now.

You can also test any domain right away using our free Is This Website Down? Checker.

The 5 Most Common Reasons Websites Go Down§

Understanding why websites crash or become unreachable helps demystify error messages and guides your troubleshooting process. Every web request travels through multiple layers of internet infrastructure:

[Your Device] → [Local Router] → [ISP DNS Resolver] → [Internet Backbone / BGP] → [Cloudflare / CDN] → [Origin Web Server] → [Database Engine]

A failure at any single point in this chain can break connectivity. Here are the five primary culprits:

1. DNS Resolution Failures & Propagation Lags§

The Domain Name System (DNS) is the internet's phonebook, translating human-friendly names like example.com into machine-routable IP addresses (IPv4 93.184.216.34 or IPv6 2606:2800:220:1:248:1893:25c8:1946).

When a website administrator updates nameservers, modifies an A record, or migrates hosting providers, global DNS propagation can take anywhere from a few minutes to 48 hours. If your ISP's recursive DNS cache holds stale or invalid records, your browser will fail to establish a connection even if the remote server is completely healthy.

2. CDN & Edge Proxy Outages§

Modern high-traffic websites rarely serve requests directly from bare-metal origin servers. Instead, they rely on Content Delivery Networks (CDNs) and Reverse Proxies like Cloudflare, Fastly, AWS CloudFront, or Akamai.

If the edge CDN suffers an incident or if the edge cannot reach the origin web server over the private backhaul, users will receive a CDN error page (such as Cloudflare's Error 521 "Web Server Is Down" or Error 522 "Connection Timed Out").

3. Web Server Overload & Application Crashes§

Sudden viral traffic spikes, Distributed Denial of Service (DDoS) attacks, memory leaks, unhandled code exceptions, or exhausted database connection pools can cause web servers (Nginx, Apache, Node.js, Caddy, IIS) to freeze or drop incoming TCP connections.

When an application server runs out of workers or memory, it halts request processing, yielding 500 Internal Server Error or 503 Service Unavailable.

4. Expired SSL/TLS Certificates§

Modern web browsers enforce strict HTTPS protocols via HTTP Strict Transport Security (HSTS). If a webmaster forgets to renew an SSL certificate or if an automated Let's Encrypt renewal script fails, browsers will deliberately block access with aggressive warning screens (NET::ERR_CERT_DATE_INVALID or SEC_ERROR_EXPIRED_CERTIFICATE). While the server is technically online, normal users cannot safely proceed.

5. Routing Incidents & BGP Hijacking§

Border Gateway Protocol (BGP) governs how data packets navigate between autonomous internet systems (ASNs). Accidental route misconfigurations or BGP leaks can cause traffic bound for specific servers to be routed into black holes, isolating entire regions of the globe from accessing certain websites.

Client vs. Server Outage: How to Tell the Difference§

Before attempting to contact support or waiting indefinitely, run through this diagnostic matrix:

Symptom Probable Cause Scope Quick Diagnostic Test
DNS_PROBE_FINISHED_NXDOMAIN Local DNS cache or domain expiration Local / Global Test domain with NexaTools Ping
502 Bad Gateway / 504 Gateway Timeout Origin server down behind reverse proxy Global Check server status or official status page
ERR_CONNECTION_TIMED_OUT Firewall, ISP blocking, or dead server Local / Regional Try mobile data or a VPN
Site loads on phone (4G/5G) but not home Wi-Fi Local ISP DNS cache or router issue Local only Flush DNS or switch to 1.1.1.1
Site loads partially (text loads, images broken) CDN asset host or third-party script failure CDN / Origin Inspect browser DevTools Network tab

Step-by-Step Troubleshooting Checklist for Users§

If a website is unreachable for you, follow these 6 proven steps in order:

Step 1: Check with an Independent External Checker§

Never rely solely on your own browser tab. Local browser cache, service workers, cookies, and local DNS often disguise real server health.

  1. Open the NexaTools Is This Website Down? Tool.
  2. Enter the domain name (e.g. github.com or apple.com).
  3. Click Check Status.

Our tool probes the target server from low-latency global cloud edge nodes, performing concurrent DNS queries, HTTP/HTTPS handshakes, and response time measurements. If our tool reports UP, the site is operational and the block is on your end. If it reports DOWN, the website's engineering team is already responding to an outage.

Step 2: Test via Mobile Data (Bypass Local Wi-Fi)§

Disconnect your smartphone from your home or office Wi-Fi network and switch strictly to cellular data (4G/5G/LTE).

  • If the website loads on cellular data, your local router, local ISP DNS, or company firewall is intercepting or failing the connection.
  • If the website fails on both cellular and Wi-Fi across different service providers, it is virtually certain to be a global or wide-area outage.

Step 3: Perform a Hard Refresh & Clear Browser Cache§

Modern browsers aggressively cache static assets, 301 redirects, and service worker responses. A regular refresh (F5 or clicking the reload icon) may simply reload the cached error.

  • Windows / Linux: Press Ctrl + Shift + R or Ctrl + F5.
  • macOS: Press Cmd + Shift + R.
  • Alternative: Open a new Private / Incognito window (Ctrl + Shift + N or Cmd + Shift + N) and visit the URL.

Step 4: Flush Your Operating System DNS Cache§

Operating systems cache IP mappings locally to accelerate browsing. If a site changed its IP address, your system might still be querying the dead IP.

On Windows:

  1. Press Windows Key + R, type cmd, and press Enter.
  2. Type the following command and press Enter:
ipconfig /flushdns
  1. You should receive: Successfully flushed the DNS Resolver Cache.

On macOS:

  1. Open Terminal (via Spotlight: Cmd + Space → Terminal).
  2. Run the command for modern macOS versions (Sonoma, Ventura, Monterey):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  1. Enter your administrator password when prompted.

On Linux (systemd-resolved):

sudo resolvectl flush-caches

Step 5: Switch to Public DNS Resolvers (Cloudflare or Google)§

Many local internet service providers (ISPs) operate slow or poorly maintained DNS servers that experience intermittent resolution failures or censor specific domains.

Switching your DNS to privacy-first, enterprise-grade public resolvers resolves many local connectivity bugs:

  • Cloudflare DNS:
  • IPv4 Primary: 1.1.1.1
  • IPv4 Secondary: 1.0.0.1
  • IPv6: 2606:4700:4700::1111 & 2606:4700:4700::1001
  • Google Public DNS:
  • IPv4 Primary: 8.8.8.8
  • IPv4 Secondary: 8.8.4.4
  • IPv6: 2001:4860:4860::8888 & 2001:4860:4860::8844

Step 6: Temporarily Disable VPNs, Proxies, and Strict Ad Blockers§

Corporate VPNs, proxy networks, and aggressive browser extensions (such as strict script blockers or misconfigured antivirus web shields) can erroneously terminate TLS connections or block CDN domains. Disable your VPN or ad blocker temporarily to verify if it is causing the drop.

Decoding HTTP Status Codes: What Do the Numbers Mean?§

When an HTTP client (like your browser) communicates with a web server, the server returns a 3-digit status code. Here is a definitive guide to the codes associated with outages and connectivity errors:

2xx Success§

  • 200 OK: The request succeeded, and the server delivered the expected payload.
  • 204 No Content: The server successfully processed the request, but is not returning any content.

3xx Redirection§

  • 301 Moved Permanently: The resource was permanently migrated to a new URI (e.g. HTTP → HTTPS).
  • 302 Found / 307 Temporary Redirect: The resource is temporarily reachable at another address.

4xx Client-Side Errors§

  • 400 Bad Request: The server cannot process the request due to malformed syntax or invalid headers.
  • 401 Unauthorized: Authentication is required and has failed or has not been provided.
  • 403 Forbidden: The server understood the request, but refuses to authorize it (often triggered by Cloudflare WAF, geo-blocking, or bad permissions).
  • 404 Not Found: The server is online and operational, but the specific URL or resource does not exist.
  • 429 Too Many Requests: The user or IP address has sent too many requests in a given amount of time (rate limiting).

5xx Server-Side Errors§

  • 500 Internal Server Error: The server encountered an unexpected condition that prevented it from fulfilling the request (e.g. backend code crash or database connection loss).
  • 502 Bad Gateway: The server acting as a gateway or proxy received an invalid response from the inbound upstream server.
  • 503 Service Unavailable: The server is currently unable to handle the request due to temporary overloading or scheduled maintenance.
  • 504 Gateway Timeout: The proxy server did not receive a timely response from the upstream backend server.

Webmaster Checklist: How to Monitor and Prevent Downtime§

If you are a developer, webmaster, or site owner, unexpected downtime damages SEO rankings, hurts brand trust, and results in lost revenue. Here are the core pillars of maintaining high availability:

  1. Implement Synthetic Health Monitoring: Use automated monitoring tools to poll your critical endpoints every 60 seconds from multiple global regions.
  2. Utilize Redundant Anycast DNS: Never rely on a single domain registrar's default nameservers. Use Anycast DNS providers (like Cloudflare or Route 53) to ensure 100% DNS uptime.
  3. Configure Multi-Region Failover: Deploy origin servers across multiple geographical availability zones with automated health-check failover.
  4. Automate Certificate Lifecycle Management: Use automated ACME clients (such as Certbot or Caddy) with auto-renewal alerts set 30 days prior to certificate expiration.
  5. Implement Robust Edge Rate Limiting: Protect backend infrastructure from volumetric layer-7 DDoS floods by enforcing rate limits at the CDN edge.

Summary & Next Steps§

When a site won't load, remember:

  1. Don't panic or assume your computer is broken.
  2. Check the domain instantly with the NexaTools Is This Website Down? Tool.
  3. Test across cellular data to isolate router vs. server issues.
  4. Flush your operating system's DNS cache and switch to 1.1.1.1.
  5. Check official status dashboards (e.g., Downdetector or status pages) if the outage is confirmed to be global.

Bookmark this page and our diagnostic tools whenever you need instant clarity during network hiccups!