Is This Website Down? 9 Ways to Check if a Website Is Down for Everyone or Just You

by API Status Check Team
Staff Pick

📡 Monitor your APIs — know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

You click a link, hit enter, and... nothing. The page won't load. Your browser spins. Maybe you get a cryptic error message, or maybe just a blank white screen.

The first question everyone asks: is this website actually down, or is it just me?

It's a question that gets searched over 50,000 times per day across Google. And the answer matters — because if the website is down for everyone, you can stop troubleshooting your own connection and just wait. But if it's only down for you, there's something on your end you can fix right now.

This guide covers nine proven methods to check if a website is down, from instant online tools to command-line diagnostics for developers. We'll also cover what to do once you've confirmed the status, how to set up proactive monitoring so you never have to wonder again, and quick-check links for the most popular services people search for.

Quick Answer: Check Right Now

Fastest method: Use a website down checker that tests from multiple global locations. If the site loads from other locations but not yours, it's a local issue. If it fails everywhere, it's down for everyone.

Check any website instantly: Visit API Status Check — we monitor 500+ popular services and APIs in real time, with response time graphs, outage history, and automated alerts.

For specific services, jump to our real-time status pages:

Service Status Page Common Search
ChatGPT Real-time monitoring "is chatgpt down"
Instagram Uptime tracking "is instagram down"
Discord Status + alerts "is discord down"
YouTube Live status "is youtube down"
TikTok Outage detection "is tiktok down"
Netflix Service health "is netflix down"
Spotify Availability check "is spotify down"
Roblox Platform status "is roblox down"
DoorDash Delivery status "is doordash down"
AWS Cloud health "is aws down"
Stripe API status "is stripe down"
GitHub Developer tools "is github down"

View all 500+ services →

-------|------------|---------------| | Cloudflare | 1.1.1.1 | 1.0.0.1 | | Google | 8.8.8.8 | 8.8.4.4 | | Quad9 | 9.9.9.9 | 149.112.112.112 |

6. Disable your VPN VPNs route traffic through different servers and can be blocked by some websites. If you're using a VPN, try disconnecting and accessing the site directly.

7. Check your hosts file If someone (or malware) modified your hosts file, it might be redirecting the domain to a wrong IP.

# macOS/Linux
cat /etc/hosts

# Windows
type C:\Windows\System32\drivers\etc\hosts

Look for entries matching the domain you're trying to reach. If you see unexpected entries, that's your problem.

Corporate Network Issues

If you're on a work network, your IT team may be blocking the site intentionally (firewall, content filter, proxy) or unintentionally (misconfigured DNS). Check with IT before spending hours troubleshooting.

Best for: Determining whether the problem is the website or something on your end.

Method 4: Use Command-Line Diagnostics

For developers and power users, command-line tools give you granular diagnostic data that no browser-based checker can match.

ping — Is the Server Reachable?

ping example.com

Reading the results:

  • Reply from [IP] — Server is reachable at the network level
  • Request timeout — Server isn't responding (could be down, or ICMP blocked)
  • Unknown host — DNS resolution failed entirely
  • High latency (200ms+) — Server is up but experiencing network issues

Caveat: Many modern web servers block ICMP/ping for security. No ping response ≠ site is down. Always follow up with curl.

curl — Is the Web Server Responding?

# Quick status check
curl -o /dev/null -s -w "HTTP %{http_code} | Time: %{time_total}s | DNS: %{time_namelookup}s\n" https://example.com

# Full headers
curl -I https://example.com

HTTP status codes decoded:

Code Meaning Website Status
200 OK ✅ Up and working
301/302 Redirect ✅ Up (follow redirect)
403 Forbidden ⚠️ Up, but access denied
404 Not Found ⚠️ Server up, page missing
500 Internal Server Error ❌ Server-side failure
502 Bad Gateway ❌ Upstream server failure
503 Service Unavailable ❌ Overloaded or maintenance
504 Gateway Timeout ❌ Upstream server timeout
Connection refused — ❌ Server not accepting connections
Timeout — ❌ Server unreachable

Pro tip: Add -L to follow redirects: curl -IL https://example.com

dig / nslookup — Is DNS Working?

# Check DNS resolution
dig example.com

# Check from a specific DNS server
dig @8.8.8.8 example.com

# Quick check
nslookup example.com

If DNS doesn't resolve the domain, the website is effectively down even if the server is running.

traceroute — Where Does the Connection Break?

# macOS/Linux
traceroute example.com

# Windows
tracert example.com

Traceroute shows every network hop between you and the server. If the trace stops partway (you see * * * for multiple hops), you can identify where the connection fails:

  • Stops at your router: Local network issue
  • Stops at your ISP: ISP routing problem
  • Stops near the destination: Server or hosting provider issue
  • Completes but slow: Network congestion somewhere along the path

mtr — Continuous Network Diagnostics

mtr example.com

MTR combines ping and traceroute into a real-time diagnostic tool. It continuously tests each hop and shows packet loss percentages, which is invaluable for identifying intermittent connectivity issues.

Best for: Developers, sysadmins, and anyone who wants to understand exactly why a connection fails, not just whether it does.

Method 5: Check Social Media and Community Reports

When a popular website goes down, the internet reacts within minutes. Social media becomes a real-time crowdsourced outage detector — often faster than official status pages.

Where to Look

Twitter/X — Search for "[service] down" or "is [service] down." During major outages, these terms trend within minutes. Look for posts from the last 15 minutes to get current status.

Reddit — Subreddits like:

  • r/sysadmin — For B2B/enterprise service outages
  • r/webdev — For developer tool outages
  • Service-specific subreddits (r/aws, r/github, etc.)

Hacker News — Major developer tool and cloud outages typically hit the front page within 30 minutes.

DownDetector — Aggregates user-submitted outage reports and shows heat maps of affected regions. Useful for consumer services.

The Social Media Signal Problem

Social media is fast but noisy. A few users complaining doesn't confirm an outage — it could be:

  • Regional ISP issues affecting multiple users in one area
  • A single viral tweet triggering "me too" responses from people who haven't actually checked
  • Scheduled maintenance that users didn't know about
  • User error (wrong password, expired subscription, etc.)

Best practice: Use social media as a signal, then verify with a direct check (Methods 1 or 4). If you see 100+ reports in 5 minutes, it's almost certainly real. If it's 5 people over an hour, investigate further.

Best for: Getting the fastest possible signal during major outages of popular services.

Method 6: DNS and CDN Diagnostics

Sometimes the web server itself is fine, but the infrastructure that routes you to it is broken. DNS failures and CDN outages can make a perfectly healthy website unreachable.

DNS Propagation Check

If a website recently changed hosting providers, moved servers, or updated DNS records, propagation can take up to 48 hours. During this window, some users can access the site while others can't.

Check propagation: Use dnschecker.org, whatsmydns.net, or our free CNAME Lookup and MX Lookup tools to see if DNS records resolve consistently. You can also run a Reverse IP Lookup to verify the hostname behind the IP.

What to look for:

  • Same IP address from all DNS servers → Propagation complete
  • Different IPs or NXDOMAIN from some servers → Still propagating
  • NXDOMAIN everywhere → Domain is not resolving (expired domain? deleted records?)

CDN Health Check

Most major websites use a Content Delivery Network (CDN). If the CDN has issues, the website becomes unreachable even though the origin server is fine.

Common CDN indicators in response headers:

curl -I https://example.com 2>/dev/null | grep -iE "server|cf-ray|x-served-by|x-cache|via"
Header CDN Provider
cf-ray Cloudflare
x-served-by Fastly
x-amz-cf-id Amazon CloudFront
x-akamai-* Akamai
x-vercel-id Vercel

If you identify the CDN, check their status page:

When CDNs go down, the blast radius is enormous. The June 2021 Fastly outage took down Reddit, Twitch, The Guardian, The New York Times, and thousands more — all because a single CDN configuration change went wrong.

Best for: Diagnosing why a website is down when the server seems fine, especially after recent infrastructure changes.

Method 7: Use Browser Developer Tools

Your browser's built-in developer tools can reveal exactly what's happening when a page fails to load — including network errors, failed requests, and slow resources.

How to Open Developer Tools

  • Chrome/Edge: F12 or Ctrl+Shift+I (Mac: Cmd+Option+I)
  • Firefox: F12 or Ctrl+Shift+I
  • Safari: Cmd+Option+I (enable in Settings → Advanced → Show Develop menu)

What to Check

Network tab: Shows every request the page makes. Look for:

  • Red/failed requests — These are the requests that broke
  • Status codes — 4xx and 5xx errors on critical resources
  • Timing — If requests are "pending" for a long time, the server is slow or unresponsive
  • Blocked requests — Ad blockers or security extensions might be preventing the page from loading

Console tab: JavaScript errors can prevent pages from rendering even when the server responds normally. If you see red error messages about failed API calls or CORS issues, the site has a client-side problem.

Security tab: SSL/TLS certificate issues can prevent page loads. If the certificate is expired, misconfigured, or from an untrusted authority, your browser will refuse to load the page.

Best for: Developers diagnosing partial failures, mixed content issues, and client-side rendering problems.

Method 8: Test from Multiple Geographic Locations

For a comprehensive answer to "is it down for everyone?", you need to test from multiple geographic regions, not just your location.

Global Testing Tools

Several free tools let you test website availability from dozens of locations worldwide:

  • API Status Check — Monitors 500+ services from multiple global checkpoints
  • check-host.net — HTTP, TCP, ping, and DNS checks from 40+ locations
  • Uptrends Free Website Test — Tests from 200+ worldwide checkpoints
  • Geoping — Visual map showing response times by region

Reading Geographic Results

Pattern What It Means
Down everywhere Global outage — server is down
Down in one region Regional issue — CDN, DNS, or routing problem
Down in one country Possible censorship, geo-blocking, or local ISP issue
Slow everywhere Server overloaded but still responding
Slow in distant regions Normal — further distance = higher latency

When Geographic Testing Matters Most

  • Global businesses serving customers worldwide
  • API dependencies your app relies on from specific regions
  • CDN issues that only affect certain edge nodes
  • Compliance — verifying content availability in required regions

Best for: Anyone who needs to confirm whether a website is down globally or just experiencing regional issues.

Method 9: Set Up Proactive Monitoring (Stop Wondering)

The best way to check if a website is down? Know about it before you even have to ask.

Proactive monitoring checks websites automatically at regular intervals and alerts you the moment something goes down. Instead of reactively Googling "is [service] down," you get a push notification within seconds.

For Services You Depend On

API Status Check RSS + Alerts: We track 500+ popular APIs and services. Subscribe to alerts for the services that matter to you:

Why this matters: If your SaaS product depends on Stripe for payments, AWS for hosting, and SendGrid for email, knowing about their outages immediately lets you communicate proactively to your customers instead of getting surprised by support tickets.

For Your Own Websites

If you run websites or APIs, you need automated monitoring:

🔧 Need production-grade monitoring? Better Stack combines uptime monitoring, incident management, and status pages in one platform. Monitor from 20+ global locations with 30-second check intervals and get alerts via Slack, email, SMS, or phone call. Trusted by thousands of engineering teams.

What to monitor:

  • HTTP/HTTPS response codes — Detect 5xx errors and timeouts
  • Response time — Alert when pages take longer than your threshold (e.g., 3 seconds)
  • SSL certificate expiry — Get warned 30 days before your cert expires
  • DNS resolution — Detect domain resolution failures
  • Content verification — Check that specific text appears on the page (catches partial failures)
  • API health endpoints — Monitor /health or /status endpoints

Recommended check interval: Every 1-3 minutes for production services, every 5-10 minutes for non-critical sites.

Best for: Anyone who can't afford to discover downtime from their users. Prevention beats reaction — always.

🔐 Protect your accounts during outages. When services go down, phishing attacks spike — scammers send fake "service restored" emails. Use 1Password to manage unique, strong passwords for every service and enable 2FA everywhere. Never click password reset links during an active outage.

What to Do When a Website IS Down

You've confirmed it — the website is genuinely down. Here's what to do next, depending on who you are.

If You're a Regular User

  1. Don't panic or keep refreshing. Hammering F5 actually makes outages worse by adding load to struggling servers.
  2. Check for announcements. Look at the service's Twitter/X account or status page for updates and estimated recovery times.
  3. Find temporary alternatives:
    • Streaming down? Try a different service (Netflix → Disney+, Spotify → YouTube Music)
    • Email down? Use an alternative client or the mobile app
    • Payment service down? Use a different payment method
  4. Set an alert. Use API Status Check to get notified when the service recovers instead of manually checking every 5 minutes.
  5. Document the impact. If you're affected by a service outage with an SLA (paid service), screenshot the downtime evidence for potential credits.

If You're a Developer or Business Owner

  1. Assess the blast radius. Which features, workflows, and users are impacted?
  2. Check your dependency chain. Is it your server, or a third-party service you depend on? Use curl to test each dependency independently.
  3. Activate your incident response plan. Update your own status page, notify affected users, and post to your support channels.
  4. Implement graceful degradation. Can you serve cached content? Can you disable the broken feature without taking down the whole app? Circuit breakers and retry logic are your friends.
  5. Communicate proactively. Customers are more forgiving of downtime when you communicate clearly and promptly.
  6. Run a post-mortem. After recovery, document what happened, why, and what you'll do to prevent it. This is where real improvement happens.

📖 Related guides:

Most Searched "Is It Down?" Services

These are the services people check most frequently. We monitor all of them in real time:

Social Media & Communication

Streaming & Entertainment

AI & Developer Tools

Cloud & Infrastructure

Finance & Payments

Productivity & Business

Internet & Telecom

Browse all 500+ monitored services →

Frequently Asked Questions

How do I check if a website is down for everyone or just me?

Use a multi-location website checker like API Status Check. These tools test the website from servers in different geographic regions. If the site loads from other locations but not yours, it's a local issue — try clearing your DNS cache, switching networks, or disabling your VPN. If it fails from all locations, the website is down for everyone.

What does "503 Service Unavailable" mean?

A 503 error means the web server is running but can't handle your request right now. This usually indicates the server is overloaded with too much traffic, undergoing scheduled maintenance, or a backend service (database, API) has failed. It's typically temporary — try again in a few minutes.

Why can I access a website on my phone but not my computer?

This usually means the issue is with your computer's network configuration, not the website itself. Common causes: corrupted DNS cache (flush it), a browser extension blocking the site, a VPN routing traffic differently, your hosts file redirecting the domain, or your firewall blocking the connection. Try incognito mode first to rule out extensions.

How long do website outages typically last?

Most unplanned outages resolve within 30 minutes to 2 hours. Major cloud provider outages (AWS, Cloudflare, Google Cloud) can last 2-6 hours. Planned maintenance windows are usually scheduled during low-traffic hours (2-6 AM local time) and last 1-4 hours. The longest outages tend to be caused by data center failures, BGP routing issues, or cascading failures across distributed systems.

Can a website be partially down?

Yes, and this is actually more common than a complete outage. A website might have its homepage working but its API failing, its login system down but its static pages available, or its service working in one region but not another. This happens because modern websites are built from many independent components (web servers, databases, CDNs, third-party APIs, authentication services). Any one of these can fail independently.

Why does a website work when I use a VPN?

If a website loads with a VPN but not without one, the issue is between your ISP and the website's server. Possible causes: your ISP is blocking the domain (censorship or content filtering), there's a routing issue between your ISP and the hosting provider, or DNS filtering is preventing resolution. The VPN routes traffic through a different path, bypassing the broken route.

What's the difference between a website being down and being slow?

"Down" means the server isn't responding at all — you get connection timeouts, error pages, or no response. "Slow" means the server is responding, but taking much longer than normal (10+ seconds per page load). Both hurt user experience, but the causes are different. Downtime is usually caused by server crashes, network failures, or configuration errors. Slowness is usually caused by traffic spikes, resource exhaustion (CPU/memory), slow database queries, or CDN issues.

How can I get notified when a website comes back up?

Instead of manually refreshing every few minutes, set up automated alerts. API Status Check offers RSS feeds and notification integrations for 500+ services. For arbitrary websites, use uptime monitoring tools like Better Stack that alert you the moment a site recovers. You can also use the watch command on the command line: watch -n 30 'curl -s -o /dev/null -w "%{http_code}" https://example.com' to check every 30 seconds.

Stay Ahead of Downtime

You shouldn't have to Google "is [website] down?" every time something breaks. The modern approach is proactive monitoring — knowing about outages the moment they happen, before they impact your work, your business, or your evening binge-watch.

For tracking services you depend on: API Status Check monitors 500+ APIs and services in real time. One dashboard, real-time status, outage history, RSS feeds, and alerts. Check it once and you'll never manually search "is it down right now" again.

For monitoring your own websites: Set up automated checks from multiple global locations with alerts to your preferred channels. Better Stack makes this trivial.

Because downtime is inevitable. Being caught off guard isn't.

🛡️ During outages, protect yourself from phishing. Scammers send fake "verify your account" and "service restored" emails during major outages. Use a password manager like 1Password to avoid clicking phishing links — if 1Password doesn't auto-fill on a page, it's probably not the real site.

🛠 Tools We Use & Recommend

Tested across our own infrastructure monitoring 200+ APIs daily

SEMrushBest for SEO

SEO & Site Performance Monitoring

Used by 10M+ marketers

Track your site health, uptime, search rankings, and competitor movements from one dashboard.

“We use SEMrush to track how our API status pages rank and catch site health issues early.”

From $129.95/moTry SEMrush Free
View full comparison & more tools →Affiliate links — we earn a commission at no extra cost to you
See all recommended developer tools →

API Status Check

Stop checking API status pages manually

Get instant email alerts when OpenAI, Stripe, AWS, and 100+ APIs go down. Know before your users do.

Start Free Trial →

14-day free trial · $0 due today · $9/mo after · Cancel anytime

Browse Free Dashboard →