What this check does
Each region sends a single GET request with the same user agent our monitors use, follows up to five redirects and records the final status code and the total time. A status below 400 counts as up; a 4xx or 5xx is shown with its code; a timeout, refused connection, DNS failure or TLS error is shown as no response. A region whose probe is offline at that moment is marked as such rather than guessed.
How to read the result
The result box sums up the regions that checked, and the table shows what each of the 3 regions saw on its own:
- Up · HTTP 200The region got a response below 400. The response time next to it is the total time the request took, so compare it across regions: one region much slower than the rest usually points to distance or a slow network path, not a problem with the site.
- Responded with HTTP 4xx or 5xxThe server answered, but with an error such as 403 Forbidden, 404 Not Found or 503 Service Unavailable. The site is reachable but not working for that request, and the check counts as failing.
- No responseThe region got no answer at all: the name did not resolve, the connection was refused or timed out, or the TLS handshake failed. The reason is shown under the badge.
- Region offline or did not reportOur checker in that region was unavailable or did not answer in time. That row says nothing about your site.
When every region that checked got a good response, the summary says the site is reachable from all of them and gives the fastest and slowest response times. When every region failed, the site is down or unreachable from everywhere we can see. A mixed result is the interesting one: see what to do below.
Why one location is not enough
A single vantage point cannot tell a real outage apart from a problem on the path to it: a congested transit link, a regional CDN fault, or a firewall rule that blocks one cloud provider. Comparing regions separates the two. That is the same idea behind how SutramX decides to alert, explained in how we check.
What to do when one region fails
- Run it againA single failure can be a passing network blip. If the same region fails twice in a row, treat it as real.
- Read the failureA “No response” that mentions DNS means the name did not resolve from that region: compare the records with the DNS checker. A certificate error is worth a look with the SSL expiry checker.
- Look for a blockA quick 403 from one region while the others succeed often means a WAF or bot-protection rule is turning away that region's network. If it is your site, SutramX publishes its checker addresses and user agent so you can allow them.
- Suspect the edgeIf the site sits behind a CDN or geo-DNS, a failure in one part of the world often comes from the edge or route serving that region. Your provider's status page is the next place to look.
Testing uptime once vs measuring it
This page tells you whether a site is up at the moment you ask. Uptime is a different number: the share of time the site was up over a month or a year, which only continuous checks can measure. The guide what is uptime? explains the formula and what counts as downtime, and the SLA uptime calculator turns a percentage such as 99.9% into the downtime it allows.
A SutramX monitor runs this check on a schedule from the regions your plan includes and only alerts when enough of them agree the site is down. See pricing for the regions and intervals on each plan.
Frequently asked questions
How do I test my website's uptime?
Enter the address in the box above and run the check. Each SutramX probe region sends one request and reports the status code and response time it got, which tells you whether the site is up right now. An uptime percentage needs checks over time: an uptime monitor repeats the check on a schedule and records every result. Free includes 50 monitors checked every 3 minutes from 1 region, 1 status page.
What counts as up?
A response below 400, after following up to 5 redirects. A 4xx or 5xx response is shown with its code and counts as failing. A timeout, refused connection, DNS failure or TLS error is shown as "No response".
Why does one region fail when the others succeed?
Usually because of something between that region and the site rather than the site itself: a routing or transit problem, a CDN edge or geo-DNS fault in that part of the world, or a firewall rule that blocks the cloud provider the region runs on. Run the check again; if the same region keeps failing, people near it are probably affected too.
Is this website uptime checker free?
Yes, with no signup. Checks are rate limited per visitor and per site, only ports 80, 443, 8080 and 8443 can be checked, and private, loopback and link-local addresses are refused.
Does one check tell me my uptime percentage?
No. A single check is a snapshot of one moment. Uptime is the share of time a site was up over a period such as a month, so it has to be measured continuously, from outside your own infrastructure.