Guides

HTTP status codes decoded: what 200, 403, 502 and no-response really tell you

Every check returns a code. Learn which ones mean the site is healthy, which mean a bot wall (not an outage), and which mean the server is actually struggling.

5 min read

“Is it down for everyone or just me?” — how to tell in 30 seconds

The classic question. A step-by-step method using an independent checker, a second network, and DNS checks to pinpoint whose side the failure is on.

4 min read

Uptime: what “99.9%” really means

How uptime is measured, how much downtime each “nine” allows per year, and why a 100% self-check log can still hide real outages.

6 min read

Site won’t load, but a VPN fixes it — what that tells you

Diagnose regional blocks, ISP filtering, and geo-restrictions — and combine a VPN with a server-side check to pinpoint the cause.

6 min read