How to read the result
The result box gives the overall verdict, and the table shows what each of the 3 regions saw on its own:
- Up · HTTP 200The region got a response below 400, after following up to 5 redirects. The response time is the full request, including DNS lookup, connection and TLS.
- 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 this counts as failing.
- No responseThe region could not get any answer: the name did not resolve, the connection was refused or timed out, or the TLS certificate was invalid, expired or did not match. 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. These regions are left out of the verdict; they say nothing about the site.
The verdict follows from the regions that did check: up when all of them got a good response, looks down for everyone when none did, and down in some regions when the answers were mixed. If the name does not resolve at all, the form says so before any region checks it.
Is it a vendor like Stripe, Razorpay or AWS?
If your site depends on a payment gateway, cloud or AI API, the problem may be theirs. The live vendor status pages show whether Stripe, Razorpay, AWS, OpenAI and about 80 other vendors are failing for several SutramX customers right now.
Common causes and what to do next
- DNSA “No response” that mentions DNS means the name did not resolve from that region. Look up the A and CNAME records with the DNS checker; a recent change may still be propagating, or the record may be missing.
- TLS certificateA certificate error means browsers will warn too. Check the expiry date and that the certificate covers the exact host name with the SSL checker.
- Firewall, WAF or bot protectionA 403, or no response from every region while the site loads in your browser, often means automated or data-centre traffic is being blocked. If it is your site, SutramX publishes its checker addresses so you can allow them.
- Server errorsA 500, 502, 503 or 504 from every region points at the application, its upstream or the load balancer rather than the network.
- Regional outagesFailures from one or two regions only usually mean a CDN edge, routing or geo-DNS problem in that part of the world.
If it is up everywhere but not for you
- Try another networkSwitch from Wi-Fi to mobile data. If it loads, your network or ISP is the problem.
- Flush DNSYour resolver may hold an old address. Compare answers with the DNS checker.
- Clear the cache or try a private windowA stale cached page, cookie or service worker can look like an outage.
- Check for blockingCorporate proxies, VPNs and browser extensions sometimes block sites.
If it is down in some regions only
A partial failure usually means a regional network, CDN or DNS problem rather than the site itself being off. These are exactly the cases where a single-location monitor raises a false alarm, or misses a real regional outage. Read how SutramX confirms an outage across regions.
Frequently asked questions
Why does the site load for me but show as down here?
The site may be blocking automated requests or traffic from data centres: a firewall, WAF or bot-protection rule, or a country block, can turn away the checker while letting your browser through. A block that answers with an error page shows as "Responded with HTTP 403" (or similar); one that drops the connection shows as "No response".
Does a 404 or 500 count as down?
Yes. Any response of 400 or above is shown as "Responded with HTTP" and the code, and counts as failing. Anything below 400 counts as up, and redirects are followed, up to 5.
Can I check an internal site or a non-standard port?
No. Private, loopback and link-local addresses are refused, and only ports 80, 443, 8080 and 8443 can be checked. To watch an internal service, expose a health endpoint to the internet or use a heartbeat monitor that your service calls.
How is this different from uptime monitoring?
This tool sends one request from each region when you ask. An uptime monitor checks on a schedule, retries a failure and confirms it before opening an incident, then alerts you and tells you when the site recovers.
Is it your own site?
Then you should hear about it before your customers do. A free SutramX monitor checks it every few minutes and alerts you by email, Slack, Microsoft Teams, Discord or Telegram. See how uptime monitoring confirms an outage before it alerts.