How to Check if a Website Is Down (For Everyone or Just You)

You try to load a website and it just... doesn't. Is the site down? Is it your internet? Your browser? Your coffee?

Here's how to find out in 30 seconds — and how to make sure you're never the last to know when a service your app depends on goes dark.

The Fastest Way: Just Check

Before doing anything clever, try statusfield.com or search for the service directly. If it's a major service (GitHub, AWS, Stripe, Slack, etc.), we're already monitoring it — you'll get a real-time yes/no in seconds.

For services not in our catalog, here are 6 reliable methods:

Method 1: Use a "Is It Down?" Checker

These tools test the site from their own servers, not yours. If it loads for them but not you, the problem is on your end.

• Statusfield — monitors 1,500+ services in real-time
• downforeveryoneorjustme.com — simple, does what it says
• isitdownrightnow.com — shows recent history too

Just paste the URL and hit check. If it loads remotely but not locally, skip to the "it's just me" section below.

Method 2: Try a Different Network

This is the fastest self-diagnosis:

1. Turn off WiFi on your phone and use mobile data
2. Try the site

If it loads on mobile data but not your WiFi, the problem is your network — likely your ISP, router, or DNS. If it doesn't load on either, the site is probably actually down.

Method 3: Ping the Domain

Open Terminal (Mac/Linux) or Command Prompt (Windows) and run:

ping github.com

If you get responses, your DNS is resolving the domain and the host is reachable at the network level. If you get Request timeout or Host not found, the site is either down or your DNS is broken.

Note: Some sites block ping (ICMP) intentionally. No ping response doesn't always mean the site is down.

Method 4: Check the HTTP Status Code

More precise than ping — this tests the actual web server:

curl -I https://github.com

You're looking for HTTP/2 200 or HTTP/1.1 200 OK in the response. Other codes that matter:

A 503 or 504 almost always means the site has real problems. A 500 means the server is running but something is broken in the application.

Method 5: Check Their Status Page

Most major services have a status page. Usually it's at status.{domain}.com or {domain}.com/status. Examples:

• GitHub: githubstatus.com
• AWS: status.aws.amazon.com
• Stripe: status.stripe.com
• Cloudflare: cloudflarestatus.com

Caveat: These pages can lag 15–30 minutes behind actual incidents. Companies investigate internally before posting public updates. For real-time status, third-party monitoring is more reliable.

Method 6: Check Social Media

Search Twitter/X for [site name] down sorted by Latest. Within minutes of a major outage, hundreds of users start posting. It's the fastest signal available — faster than official status pages.

Reddit is also useful for prolonged outages; subreddits like r/github or r/aws often have ongoing threads.

If It's Down For Everyone

The site is genuinely down. Now what?

For sites you depend on personally: just wait. Check back in 15–30 minutes. Major services resolve most outages in under an hour.

For services your app or business depends on: this is where you need a plan.

• If your app shows end-users an error, add messaging that clarifies it's a vendor issue, not yours.
• Have a runbook for your most critical dependencies. What do you do when Stripe goes down? When Auth0 fails? When your email provider is offline?
• Consider graceful degradation: can your app function in a limited capacity when dependency X is down?

If It's Down Just For You

Good news: the site itself is fine. Here's how to fix your local issue:

Clear DNS Cache

Sometimes your computer is caching a bad DNS record.

Mac:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Windows:

ipconfig /flushdns

Linux:

sudo systemd-resolve --flush-caches

Try a Different DNS Server

Your ISP's DNS might be having issues. Switch temporarily to:

• Google DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1

On Mac: System Preferences → Network → Advanced → DNS.

Check Your /etc/hosts File

On Mac/Linux, run:

cat /etc/hosts | grep [sitename]

If the site appears there with a wrong IP (maybe from an old local dev setup), that's your problem. Remove or comment out the line.

Disable VPN or Proxy

VPNs and corporate proxies route traffic through their own servers. If those servers have issues, sites can appear down. Disconnect from your VPN and try again.

Try Incognito / Private Mode

Browser extensions, cached responses, and cookies can all cause sites to fail to load. Open a private window — this bypasses extensions and uses a fresh cookie/cache state.

Restart Your Router

Boring but effective. Power cycle your router (unplug it, wait 30 seconds, plug back in). Fixes a surprising number of "the internet is broken" situations.

Set Up Automatic Monitoring (So You're Never Caught Off Guard)

Manually checking if sites are down is fine for one-off situations. But if you have services your business depends on — Stripe, AWS, Slack, GitHub, Twilio, whatever — you should be getting automatic alerts when they go down.

Statusfield monitors 1,500+ services in real-time and sends you an alert the moment something goes down. You can:

• Pick exactly which services and components you care about
• Get alerts via email, Slack, Discord, or webhooks
• See all your dependencies on one dashboard
• Stop being the last person to find out about outages

Takes 2 minutes to set up.

Start monitoring your dependencies →

Quick Reference: "Is This Site Down?" Decision Tree

Site not loading?
│
├── Does it load via mobile data?
│   ├── YES → Problem is your network/DNS, not the site
│   └── NO → Site might be down
│
├── Does it load via a "is it down" checker?
│   ├── YES → Problem is local to you (see "just for me" section)
│   └── NO → Site is probably down globally
│
└── Is there a status page or social media activity?
    ├── YES + confirms outage → Wait it out
    └── NO activity → Could be a small incident; try again in 15 min

Frequently Asked Questions

Why does a site load on my phone but not my laptop?

Usually DNS. Your phone uses your carrier's DNS, your laptop uses your home network's DNS. Try flushing your laptop's DNS cache or switching to 8.8.8.8.

Why does a site load sometimes but not others?

Intermittent failures often mean the site is partially down (some servers working, some not). This shows up as 503 errors or timeouts. Also check if you have a flaky network — run ping 8.8.8.8 and watch for packet loss.

The site loaded but looks broken. Is it down?

Not fully. But it could be partially down — a CDN issue, a broken JavaScript file, or a backend service that's failing silently. Check their status page for "degraded" components.

I'm a developer. How do I check a site my app depends on?

Use health checks and circuit breakers in your code, plus external monitoring like Statusfield for alerting. Don't rely on manual checks — you'll find out too late.

Is "ping" a reliable way to check if a site is down?

No, ping only tests network reachability at the IP level. Many sites block ICMP (ping). Use curl -I for a more accurate HTTP-level check.