HTTP status & speed check
Check whether a site is up, its HTTP status code, and where its response time goes.
Enter a URL and we request it once, report the HTTP status code it answers with, and break the response time into the stages that make it up.
What this checks
- Whether the site is reachable and the HTTP status code it returns.
- The total response time, and how it splits across DNS, TCP, TLS, and server processing.
- Whether the response is a success, a redirect, a client error, or a server error.
Why it matters
A status code is the quickest read on a site's health: 2xx is healthy, 4xx means the request was rejected, and 5xx means the server itself failed. When a site is up but slow, the timing breakdown points at the cause, whether it is DNS resolution, the TLS handshake, or the server taking too long to respond. That is the difference between guessing and knowing where to look.
Frequently asked questions
Can't find your answer? Get in touch.
This is a one-time snapshot.
Ranetrace runs this check around the clock and tells you the moment something changes, so you hear about a problem before your visitors do. Monitoring for Laravel and PHP apps, from the outside and the inside.