Slow website vs actually down

Last updated: 1 September 2026

A site can feel broken long before it disappears entirely. Pages load in seconds instead of milliseconds, assets hang, or only some features fail. Slowness is not the same as down, and isitdown.me measures both ideas differently.

What we measure

Each check records response time in milliseconds for a single HTTPS request to https://domain/. We also assign UP, DOWN, or DEGRADED from whether we got an HTTP response and which status class it fell into.

Slowness on your side vs theirs

High response time on isitdown.me suggests the origin or path from our datacentre is slow. If our time looks good but your browser crawls, look locally: Wi-Fi quality, VPN, DNS, ad blockers, or heavy pages with large scripts (we do not execute JS).

Conversely, if we report high milliseconds or timeouts while you are fine, our route to the host may differ from yours. That is why “everyone or just you” still matters. See the companion guide.

Partial failures

APIs, CDNs, or regional edges may fail while the homepage returns 200. Our check does not crawl every endpoint. A UP homepage does not prove checkout, login, or mobile apps work.

Using history wisely

Domain pages show recent check times when enough visits exist. Spikes in response time alongside 5xx codes point to instability. Flat UP with rising milliseconds can warn before hard failure.

FAQ

Do you alert when a site slows down? No. Checks run when someone visits the tool or opens a domain page that needs a fresh probe. There is no always-on alerting product here.

Is timeout the same as down? Yes on isitdown.me. If we cannot finish the HTTPS attempt within the configured window, we report DOWN.

Test response time yourself: check a domain on the homepage, then open its /domain page for context.

Check a domain

Run a live reachability check on the isitdown.me homepage, or open a saved status page at /your-domain.com.

All guides · Back to home