Check details and timing

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 — which the geo-checks map surfaces directly and which are available through the API for any check.

Fields on a check record

• status — true for up, false for down
• statusCode — HTTP status code for HTTP monitors
• responseTime — total request duration in ms
• message — success message or error string
• timings — got timing object with DNS, TCP, TLS, firstByte, and download phases
• createdAt — 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 Advanced matching is enabled and the response body matches the configured rule. 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.