Is it down, or just me?
Type a website address below and open its live status page. We check it from our own status servers the moment the page loads, so you can tell a real outage from a local problem.
Quick checks
How the check works
1. You type an address
We turn what you typed into a domain and take you to that site’s status page — a shareable link you can send to friends (“is it down for you too?”).
2. Our server checks it
This site's own backend connects to the site and records whether the server answers, with the HTTP status and response time. This is the vantage point that tells a real outage from a local one.
3. The verdict appears automatically
As soon as the status page loads, our server runs the check and shows the verdict, the HTTP status, the response time and the recent history — no extra clicks needed. Share the link and everyone gets the same picture.
Why a site can seem down
It really is down
Outages happen: server failures, DNS changes, certificate expiries, or a bad deploy. If the check fails for everyone, it usually is the site — wait a while and re-check.
It is only you
Local causes produce the same red screen: a flaky connection, a VPN that breaks DNS, a corporate firewall, an ad blocker in aggressive mode, or outdated system time that fails certificate checks.
It is regional
Some outages affect a single country or ISP. The check reflects what is reachable from your network — a friend on another network can compare notes quickly.
It is slow, not down
A site under heavy load may answer after our 10 second window. In that case the check says “unreachable” while the site is merely slow. Re-checking later clears it up.
Frequently asked questions
Is this website status checker really free?
Yes. The tool is free and unlimited — you can check as many addresses as you like, as often as you like, with no account.
Do you see or store the websites I check?
Yes — the domain you check goes to this site’s own backend so it can run the check. It keeps only the last few results in memory (a few seconds of caching plus a short history for the chart). Nothing is written to disk, no account is created, and the in-memory results reset on every deploy.
Our servers can’t reach a site that I can open — why?
Our check runs from a single vantage point. A site can be up for you while our server sees a problem — for example a firewall, bot protection, or a certificate that our server doesn’t trust. The verdict tells you exactly which step failed (DNS, connection, TLS or timeout).
Can I check IP addresses or local addresses?
Public IP addresses work. Private addresses (your router, 127.0.0.1, intranet names) are refused for security reasons, since the check runs from our servers and must not be able to probe your local network.
How accurate is the response time?
It is the round-trip time of a single request from our server to the site, so it reflects our connection and the site’s load at that moment. Treat it as a rough signal, not a benchmark.