What's the difference between "failed" and "errored"?

"failed" means we reached your target and it returned an error (a DNS, TCP, or TLS failure, or an HTTP status of 400 or higher). "errored" means RegionCheck's own pipeline could not get a usable result from a worker — an infrastructure problem on our side, not your target.

Why does a region show "blocked"?

The target resolved to a private, loopback, link-local, or otherwise reserved IP range, or used a port outside the allowed list (80, 443, 8080, 8443). RegionCheck blocks these to prevent probing internal networks.

What does TTFB measure?

Time to first byte is measured from the HTTP request, so it excludes the DNS, TCP-connect, and TLS-handshake times, which are reported separately.

Understanding results

Each region returns a structured result. This page explains the fields, the overall run statuses, and how to read a failure.

Result fields

Every result carries the same set of fields, whether the check succeeded or failed. Raw details are always included so you can dig into exactly what happened, not just a pass/fail summary.

Field	What it holds
url	The target URL that was checked.
resolved_ips	The IP addresses the target hostname resolved to.
dns_ms	Time spent on DNS resolution.
tcp_connect_ms	Time spent establishing the TCP connection.
tls_handshake_ms	Time spent on the TLS handshake.
ssl	Certificate detail: subject, issuer, subject alternative names, validity window, and fingerprints.
http_status	The HTTP response status code.
ttfb_ms	Time to first byte of the HTTP response.
response_headers	The response headers.
providers	Any detected CDN or bot-protection provider in front of the target.
cache_state	Whether the response looked like a cache hit or miss, based on response header evidence.
http_via	Whether the response came from the primary request or the browser-impersonation fallback.
error	The error message, when the check failed at any phase.

Run statuses

A run's overall status summarizes what happened across its regions:

success — the target responded, and no region reported a measurement error.
failed — the target was measured and the check failed: a DNS, TCP, or TLS error, or an HTTP status of 400 or higher.
partial — some regions succeeded and some failed.
errored— RegionCheck's own pipeline never got a usable result from a worker. This is an infrastructure problem on our side, not a problem with your target.
rate_limited — the target itself throttled the check.
running — a scheduled run that is still in flight.

The distinction between failed and errored matters: failed is a real signal about your target, while erroredmeans RegionCheck couldn't complete the measurement at all.

What the errors mean

Within a result, the error field explains what went wrong at a specific phase — DNS resolution, the TCP connection, the TLS handshake, or the HTTP request itself.

Two error strings are worth calling out specifically: blocked means the target or port was not allowed to be probed at all (it was never attempted), and timeout means the check ran out of its time budget before finishing.

blocked and timeoutare not run statuses — they're the error text recorded for a region when the target was rejected before probing, or the check ran out of time.

Frequently asked questions

What's the difference between "failed" and "errored"?: "failed" means we reached your target and it returned an error (a DNS, TCP, or TLS failure, or an HTTP status of 400 or higher). "errored" means RegionCheck's own pipeline could not get a usable result from a worker — an infrastructure problem on our side, not your target.
Why does a region show "blocked"?: The target resolved to a private, loopback, link-local, or otherwise reserved IP range, or used a port outside the allowed list (80, 443, 8080, 8443). RegionCheck blocks these to prevent probing internal networks.
What does TTFB measure?: Time to first byte is measured from the HTTP request, so it excludes the DNS, TCP-connect, and TLS-handshake times, which are reported separately.