Check whether a site responds from our server in Zurich. If it answers us but not you, the problem is between you and the site — not the site itself.
Is the site down for everyone or just me?
If this checker gets a response, the site is up from our network in Zurich and the problem is closer to you — DNS, your ISP, a VPN, a browser extension, or a cached error page. Try the site from mobile data as a quick second opinion.
The checker says it is up, but I still cannot load it.
We fetch response headers only, so a site can answer us correctly and still fail in your browser — a broken script, a blocked asset, or a certificate your browser rejects will not show up here. A 200 means the server answered, not that the page renders.
How often should a site be checked?
For anything customer-facing, every minute is the usual answer: a five-minute interval means a five-minute outage can go entirely unnoticed. What matters more than frequency is confirming from a second location before alerting, or you will be woken by network blips rather than real outages.