While the main Website Overview dashboard summarizes your uptime, the Checks tab acts as your raw, chronological network ledger. It logs the exact outcome of every individual HTTP(S) ping sent to your target URL.
This view is essential for debugging intermittent packet loss, identifying regional firewall blocks, or investigating temporary server rate-limiting.
Log Controls & Filtering
At the top right of the data table, you have two tools to parse through heavy check volumes:
- Search Bar: Quickly isolate specific timestamps or filter by specific geographical locations.
- Filter Utility (funnel icon): Click to filter entries by operational status. This is incredibly useful for hiding thousands of healthy checks to instantly view only the network drops or server errors.
The Network Telemetry Table
The checks table translates every external connection attempt into four core diagnostic fields:
Column | Description |
Location | The geographical edge node that performed the ping (e.g., 🇮🇳 India, Mumbai, MH). Unlike server monitoring (which runs internally), website monitors originate from external locations. This helps you identify if an outage is global or if a specific region is being blocked by a local CDN or firewall. |
Response status code | The exact HTTP header code returned by your web server. A green 200 confirms a perfectly healthy webpage load. A red badge indicates a failure and provides the exact error type—such as a 503 (Service Unavailable), a 404 (Not Found), or a 429 (Too Many Requests), which indicates your server's rate-limiting is actively blocking traffic. |
Response time | The total network latency measured in milliseconds (ms). This calculates the time it took for the ping to travel from the edge location to your server, process the request, and return the HTTP headers (Time to First Byte). |
Checked at | The absolute date and time string down to the exact second (yyyy-mm-dd hh:mm:ss) when the external ping was executed. |