Operator Disclosure
Who runs WebsiteDown.org, what it does, and how to contact support are documented on public pages.
Read About · Contact · Contact
Is It Down for Everyone or Just Me?
Website Down Checker
Check if any site is down, offline, or having problems for just you or everyone.
We run checks from 8 global regions so you can quickly separate local issues from real outages.
Ready
Ready to run a live check.
We test reachability from our edge network and show region-level details below.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Latest Public Site Checks
Need a specific domain page? Browse All Checks.
No public checks yet. New checks will appear automatically.
Latest Sites Reported Down
Need the full live feed? View Outages Today.
No confirmed down checks yet.
Your Recent Site Checks
No checks yet. Your recent checks will appear here.
Popular Site Down Checks
Trust and Transparency
Methodology Published
We explain region coverage, verdict logic, and known limitations so teams can interpret results correctly.
Public Comparison Standards
Comparison guides include benchmark rubrics, source links, and nofollow external references.
How the Website Down Checker Works
Built for one clear question: is this site down for everyone, or only for me?
1) Multi-Region Probe Set
Every lookup runs from 8 regions: US East (IAD), US West (SFO), Europe West (CDG), Europe Central (FRA), Asia South (Singapore), Asia East (Tokyo), Oceania (Sydney), and South America (Sao Paulo).
2) Verdict Logic and Timeouts
We classify checks as Up, Down, or Mixed based on majority regional reachability and HTTP probe outcomes. Per-region probe timeout is approximately 6.5 seconds. Mixed usually indicates route, DNS, CDN, or policy asymmetry.
3) Known Limits and Next Step
Reachable does not always mean full user-journey success. Browser rendering, auth flows, and app-specific failures can still break while host-level checks pass.
Read the quick checklist · Browse all guides · Compare tools
For Teams and Automation
Move from manual checks to repeatable workflows.
API Beta Waitlist
Join early API access and share your use case, expected volume, and integration needs.
Incident Update Email
Request product and reliability updates for launch milestones and major checker changes.
Shareable Incident Evidence
Use copy/share controls in each check result to pass scoped evidence into support and on-call channels.
Featured Outage Guides
Deep-dive tutorials for incident response, diagnostics, and uptime strategy.
Frequently Asked Questions
Is Website Down Checker free to use?
Yes. WebsiteDown Checker is free for normal manual checks and you do not need an account to use it. To keep results fast and reliable, we apply fair-use rate limits and abuse protection when traffic looks automated or excessive. If you need higher-volume automated usage, the API path is the right fit.
How do I check if a website is down worldwide?
Enter the domain and run a check. We test in parallel from multiple regions and return one overall verdict plus per-region details, including status and response behavior.
If most regions fail, the outage is likely broad. If only one or two regions fail, it is usually a regional routing, DNS, filtering, or local network-path issue.
What do Up, Down, and Mixed mean?
Up means the majority of regions reached the site and received a valid response. Down means the majority failed, commonly because of DNS errors, connection failures, or timeouts.
Mixed means results are split across regions. This usually points to a partial outage, regional filtering, in-progress rollout, or temporary network incident rather than a full global outage.
How many regions do you check?
Each lookup currently checks 8 regions across independent network paths. This gives a strong signal for global versus regional incidents while keeping checks quick.
It is not every network in the world, but it is enough to catch most broad outages and make triage decisions faster.
Does this check full page rendering?
No. The checker focuses on reachability and HTTP response behavior, not full browser rendering or user flows.
A site can return a healthy HTTP response while users still hit JavaScript issues, broken assets, login/session problems, or third-party script failures. For complete validation, pair this check with a real browser test.
Why can results differ by region?
Regional differences are common. Causes include CDN edge routing, DNS resolver behavior, WAF or firewall policy, ISP peering, and short cache or propagation windows.
Some providers also challenge automated traffic differently per region. That is why one region can look healthy while another reports errors at the same moment.
Do you store my recent checks on your servers?
Your personal Your Recent Checks list is stored in your browser using local storage. We do not require an account for standard checks.
We retain limited server-side operational and abuse-prevention logs, and anonymized domain-level activity can appear in public recent activity sections. Personal account-style tracking is not required for normal usage.