Free tool
Is it down for everyone, or just me?
Enter a URL and we request it from our servers in Germany. If it loads here but not for you, the problem is likely on your network.
Free to use, limited to 30 checks per hour per IP address. Results may be cached for a few minutes. More free tools
How to read the result
- Up: the server answered with a status code below 500. A 404 or 403 still means the server is reachable.
- Down: the server returned a 5xx error, timed out after 10 seconds, or the connection failed (DNS error, refused connection, TLS failure). The error message tells you which.
- Response time: total time for the request from Germany, including DNS, connection and TLS.
If it's down only for you
Try another network (for example mobile data), flush your DNS cache, and disable VPNs or browser extensions. If the site is yours and only some users are affected, check DNS propagation, CDN configuration and firewall rules that might block certain regions.
Find out before your users do
A one-off check tells you about now. An HTTP monitor checks on a schedule, as often as every 30 seconds, re-checks failures through a second DNS resolver, and alerts your team when the site is really down — and again when it recovers.
Frequently asked questions
Where is the check run from?
Can I check internal or localhost addresses?
Why is the result the same when I check again?
Monitor this continuously — free
Asniher runs these checks on a schedule, verifies failures to avoid false alarms, and alerts you by email, Slack or Discord.