Check details and timing
Response times, status codes and timing breakdown.
Overview
Every check stores a status flag, the HTTP status code (where applicable), a response time in milliseconds and a message. HTTP checks additionally record the full got request timings: DNS, TCP, TLS, time-to-first-byte and download. The geo-checks map surfaces these directly and they are available through the API for any check.

Fields on a check record
status: true for up, false for downstatusCode: HTTP status code for HTTP monitorsresponseTime: total request duration in msmessage: success message or error stringtimings:gottiming object with DNS, TCP, TLS, firstByte and download phasescreatedAt: when the check ran
HTTP status codes
For HTTP monitors, a 2xx response passes the check by default. 3xx, 4xx and 5xx responses fail unless the code is listed as a custom "up" code. Advanced matching cannot rescue a failing status code: the status check and the body match are combined with AND, so a response must pass both. 4xx usually means a client-side misconfiguration (auth, wrong URL); 5xx is a server-side failure.
Response time charts
Monitor detail pages plot response time over the selected range. The chart is the fastest way to spot gradual degradation or confirm a fix stuck.