The monitor went red.So where do we look?
Instead of opening a terminal and running a handful of commands from your own laptop, run the same path from our vantage points: DNS, TCP, TLS, HTTP, ping and traceroute, layer by layer, side by side.
Free plan: 3 monitors and one vantage point · 14-day Pro trial
What gets run
DNS
What the name resolves to, from which resolver, and how quickly.
TCP and TLS
Does the connection complete? What is the certificate, until when is it valid, and what was negotiated.
HTTP
A plain GET with status code, timing and safe headers.
Ping, traceroute and MTR
Path quality, and how far the packets get before they stop.
Why this is safe
A network tool reachable from the internet is an attack surface if it is designed carelessly.
No free-form input
The target is read from your own monitor's address; there is nowhere to type a host, port or command.
Your monitors only
A run is possible only on a monitor belonging to your active workspace.
No command execution
There is no shell involved, and non-public addresses are rejected before anything runs.
No content exposure
HTTP diagnostics do not store the response body.
What the output gives you
Region comparison
The same path runs from several points, so a regional problem is distinguishable from a global one.
A best guess at the layer
Based on the first layer that failed, a likely location for the problem is shown.
Copyable technical output
The kind of thing you can send to your hosting provider or network operator.
Where this stops
A guess, not a verdict
The failing-layer hint is guidance; it makes no firm claim about the cause.
Run limits apply
Each workspace has a limited number of runs per hour and one active run at a time.
No effect on monitoring
These runs are stored separately and never create uptime figures, incidents or alerts.
On every plan
This is not gated by plan; viewers can read the history.
Related features
Be ready the next time it goes red
Create a monitor so the diagnostics tool is beside it from the start.
Create a free account