Find out whether a site is up or down right now, from six AWS regions at once, with the load-time breakdown and SSL expiry behind the answer.
That is the question this answers. Enter a URL and LoadFocus loads it from six AWS regions at the same time. If every region gets a response, the site is up and the problem is your network, your DNS or your browser cache. If every region fails, it is genuinely down. If some succeed and some do not, you have found a regional outage that a single-location checker would have reported as fine.
Most down-detectors check from one place. A site can be perfectly healthy from Frankfurt and unreachable from Singapore because of a routing problem, a CDN edge failure or a regional deployment that did not finish. Checking six regions at once turns a yes-or-no answer into a map of who can actually reach you.
A 2xx status code means the server answered normally. A 4xx means the page is missing or blocked, a 5xx means the server itself failed, and no response at all means the host could not be reached. The timing breakdown shows where the wait came from: DNS lookup, TCP connect, TLS handshake, time to first byte, then download.
This is a snapshot of one moment. Outages rarely happen while you are looking. Point the same URL at the LoadFocus free plan and the identical check runs every minute from 25+ regions, with alerts by email, Slack, Microsoft Teams or webhook, so you hear about it before your customers tell you.
Related: API Monitoring · Status Pages · SSL Checker · UptimeRobot alternative
A status check returns more than up or down. These are the values worth reading:
How the server answered. 2xx is success, 3xx is a redirect, 4xx means the page is missing or refused, 5xx means the server broke. A site that returns 200 but renders an error page still counts as up here, which is why the status code alone is never the whole story.
How long the request took end to end. Under 1 second is healthy for a web page, and past 3 seconds visitors start leaving. Compare it between regions rather than judging one number on its own.
How quickly the server started answering. Under 800 ms is good. A slow TTFB caps everything that follows and usually means slow server-side work, a cold cache or an overloaded database.
The cost of setting up the connection before any content arrives. High DNS time is a resolver problem rather than a server one. High TLS time points to certificate chain or handshake overhead.
Days left before the HTTPS certificate expires. An expired certificate takes a site offline for every visitor at once, with no warning and no partial failure, which makes it the single most preventable outage there is.
The gap between the fastest and slowest region is what your global audience actually experiences. A quick result from one region says nothing about the rest of the world.