Website Availability by Region

Server assisted New Website & HTTP Diagnostics

Sends one HTTP request (HEAD or GET) to your URL from up to 10 Globalping community probes in the continents, regions, countries or networks you pick, and reports for each probe whether it got an answer, the status code, the address it reached and the time spent on DNS, TCP connect, TLS and the first byte. It shows how the site answers from those places at that moment: one measurement, not a monitoring history. Measurement parameters and results are public on Globalping.

Privacy: The host and options you enter are sent from the Mutqan server to Globalping, a public measurement network whose volunteer probes run the test. Globalping publishes measurement parameters and results, so do not enter anything private. Mutqan stores nothing.

How do you tell whether a website is up for everyone?

Request it from several networks outside your own: if probes in different places get an HTTP answer — a 2xx or 3xx status in the sense of RFC 9110 — the site is up from there, and a failure only on your side points at your own connection, resolver or ISP. One round of requests is a snapshot; knowing that a site stays up needs monitoring, which repeats such probes on a schedule and alerts on failures.

How to use Website Availability by Region

  1. Enter the page address (https://www.example.com/pricing). The path is requested; a query string is not sent.
  2. Pick where the probes should be, or type up to five country codes, region names or AS numbers to replace the preset.
  3. Choose how many probes to use and the method, then press Check from these locations. Results arrive within about 20 seconds.
  4. Compare the rows: a location with no response or an error status is where visitors have a problem; a location with a much slower first byte is far from your server or CDN edge.

Website Availability by Region features

  • One HTTP request to your page from up to 10 Globalping community probes, in the places you choose: five continents, the Middle East and North Africa, the Gulf countries, a single continent, or your own list of countries, UN regions and networks (AS numbers)
  • For every probe: whether it got an HTTP answer, the status code, the address it reached, and the time spent on DNS, TCP connect, TLS and the first byte
  • A summary across locations: how many probes got a successful answer, an HTTP error or no response at all, the median total time, and the fastest and slowest place
  • The error each probe reported when it got no response (a timeout, a refused connection, a name that did not resolve), named with its location
  • Works for sites behind Cloudflare and any other CDN: the probes make ordinary HTTPS requests
  • HEAD by default, GET when a server refuses HEAD; the measurement ID and the remaining Globalping quota are shown

Inputs and outputs

Inputs

  • Page URL: http:// or https:// address of a public host; its path is requested, the query string and fragment are dropped.
  • Probe locations: a preset, or up to five comma-separated country codes (SA), region names in English (Western Asia, Northern Europe) or AS numbers (AS13335) that replace it.
  • Probes: 3, 5, 8 or 10 in total. Method: HEAD (default) or GET.

Outputs

  • Summary: probes with an HTTP answer out of those that took part, successful answers, HTTP errors, probes with no response, median total time, fastest and slowest location.
  • Results by location: place, network, result symbol, status code, total, DNS, TCP, TLS and first-byte times in milliseconds, and the address the probe reached.
  • Probes without a response: the error each one reported.
  • Measurement: target, Globalping measurement ID and status, probes requested and returned, quota left and its reset time.

Website Availability by Region example

A site checked from five continents (illustrative result)

Input:

Page URL: https://www.example.com/ · Probe locations: Europe, Asia, North and South America, Africa · Probes: 5 · Method: HEAD

Output:

Probes with an HTTP answer 5 / 5 · Successful (2xx–3xx) 5 · HTTP errors 0 · No response 0 · Median total time 142 ms · Fastest 38 ms (Frankfurt, DE) · Slowest 611 ms (Lagos, NG)
Frankfurt, DE (EU) · ✓ 200 · DNS 2 · TCP 4 · TLS 11 · first byte 37 ms
Singapore, SG (AS) · ✓ 200 · first byte 140 ms
São Paulo, BR (SA) · ✓ 200 · first byte 189 ms
Ashburn, US (NA) · ✓ 200 · first byte 95 ms
Lagos, NG (AF) · ✓ 200 · first byte 598 ms

How to read the Website Availability by Region results

Every location ✓ with similar first-byte times: the page is reachable from all of them. Differences of 100–300 ms between continents are normal physics without a CDN edge nearby.

A ✗ with a 4xx or 5xx status means the server answered with an error to that location: 403 or 451 from certain countries is usually geo-blocking or a WAF rule; 5xx from one region usually means one origin or edge is failing.

A ✗ without status means no HTTP answer at all: read the probe's error. A DNS failure in one place only points at resolution there; a timeout from several places at once points at the site or its network.

One run is a snapshot. A single failing probe can be the probe's own network: run the check again before concluding that a region is down.

When to use Website Availability by Region

  • Confirm that a site, an API or a newly launched page answers from the countries where your customers are — the Gulf, Europe, Asia.
  • Check whether a CDN or geo-DNS change sends each region to the expected server, by comparing the addresses.
  • Investigate reports that "the site doesn't open in country X" from outside that country.
  • Compare first-byte times across continents before and after adding a CDN or a new region.

Troubleshooting

  • "No probe was available in these locations": the countries or networks chosen have no probe online. Use a continent or region instead, or fewer probes.
  • "The Globalping measurement network is unavailable or its hourly quota is used up": the shared hourly budget is spent; the retry time is shown when Globalping reports it.
  • "Measurements are limited to 30 per hour": this page's own limit per visitor; wait for the reset shown.
  • "The path contains characters the measurement service does not accept": check a simpler address on the same host, or the home page.
  • Every probe shows 405: the server refuses HEAD requests. Choose GET and run again.

Frequently asked questions about Website Availability by Region

Where do the requests come from?

From Globalping community probes: small agents that volunteers and companies run on home, office and data-centre connections around the world. Neither your computer nor the Mutqan server makes the request, so the result shows what visitors near those probes would get, not what you see.

Why do the probes report different addresses or status codes?

Sites behind a CDN or geographic DNS send each region to a different server, so each probe may reach another machine — the IP address column shows which. A 403 or 451 from some countries only is usually geo-blocking or a firewall rule; a 5xx from one region only points at the server or edge that serves it.

Why did fewer probes answer than I asked for?

Globalping can only use probes that are online in the locations you chose. A small country or a single network may have one probe or none at that moment; choose a wider region, or fewer probes, and run the check again.

Can I check a page behind a login or with query parameters?

No. Each probe sends a plain HEAD or GET for the path of the URL, with no cookies, no headers of yours and no query string, and a redirect is reported with its own 3xx status. A page that needs a session will show its login redirect or an error, which is what an anonymous visitor gets.

Are my checks private?

No. Globalping publishes every measurement: the target, its options and the results can be retrieved by anyone who has the measurement ID. Do not test URLs whose path is confidential. Mutqan itself stores nothing.

How often can I run it?

One visitor can start 30 measurements per hour here, each with up to 10 probes. Without a Globalping token the hourly quota is also shared with every site that uses the same server address; when it runs out the page says so, with the reset time when Globalping reports it.

Technical notes

Each probe sends one HTTP/1.1 request over TLS (HTTPS) or plain TCP (HTTP) with the method chosen and the URL's path, as RFC 9110 defines HEAD and GET; the status code classes are read as RFC 9110 defines them: 2xx success, 3xx redirection (counted as an answer and reported with its own status), 4xx client error, 5xx server error.

The timings come from the probe: DNS is its own resolver's lookup, TCP the connection set-up, TLS the handshake, first byte the wait after the request was sent, total the whole exchange. They describe the path from that probe's network, which may differ from a home connection in the same city.

Probe selection follows the Globalping API: locations are continent or UN geoscheme region names, ISO 3166-1 country codes or AS numbers; the probe count is the total for the measurement and Globalping picks which online probes serve each location. The Mutqan server rebuilds the request from allow-lists and polls the result for up to 20 seconds.

Limitations and methodology

Globalping probes run on volunteer and data-centre networks, not on your visitors' devices; their results approximate what users in that place see, and the probes assigned to a location can change from one run to the next.

One request per probe, at one moment: this is not monitoring, it keeps no history and sends no alerts. Short outages between runs are not seen.

No cookies, custom headers or request body; a redirect is reported with its 3xx status, not as the page it points to; a page that depends on JavaScript is not rendered — only the HTTP response is measured.

Measurement parameters and results are public on Globalping, and the unauthenticated hourly quota is shared with every other site using the same server address.

Security and privacy

The URL's host name and path go to the Mutqan server and from there to Globalping, which publishes the measurement. Nothing is stored by Mutqan. Do not test addresses whose path is confidential, and test only sites you are allowed to.

References

  • RFC 9110: HTTP SemanticsIETF · 2022The meaning of HTTP methods, header fields, status codes and content negotiation, independent of the wire version.
  • Globalping APIGlobalping (jsDelivr)The public API of the Globalping network: how ping, traceroute, MTR, DNS and HTTP measurements are created from community probes, located by country, region or network, and read back.
  • Monitoring Distributed Systems — Site Reliability Engineering (Rob Ewaschuk)Google / O'Reilly Media · 2016Google's SRE guidance on monitoring: black-box versus white-box monitoring and the four golden signals — latency, traffic, errors and saturation.