The summary cards at the top of Detailed Logs describe the complete applied filtered result set. They do not recalculate from only the page currently visible in the table.
Summary card definitions
| Card | Meaning |
|---|---|
| Matching rows | Every retained check satisfying the applied date range and filters |
| Up checks | Matching checks accepted as successful |
| Down checks | Matching individual failed checks |
| Avg latency | Average of matching checks that have a recorded response duration |
| Slowest | Highest recorded response duration among matching checks |
The basic count relationship is:
Up checks + Down checks = Matching rows
Rows without a response-time sample remain in Matching rows and Up or Down counts but do not contribute a duration to Avg latency or Slowest.
Full result versus current page
Suppose the applied filters match 372 checks and Rows per page is 100:
- Matching rows shows 372.
- The page status shows 100 rows on pages 1 through 3.
- Page 4 contains the remaining 72 rows.
- Up checks, Down checks, Avg latency, and Slowest continue to describe all 372 matches on every page.
This is why Down only can show 72 Down checks even when a different page size displays fewer rows at once.
How the average is calculated
Avg latency uses checks with a numeric response-time value:
sum of recorded response times / number of response-time samples
It can include a failed HTTP response if that check recorded a duration. DNS, connection, or TLS failures might not provide one.
Avg latency is not p95 response time and is not browser page-load time. Use Monitor Details for the selected range's p95 summary and response chart.
What changes the summary
The cards update when you select Apply after changing:
- Range, From, or To.
- Status.
- Diagnosis.
- Exact HTTP code.
- Error search text.
- Minimum or maximum latency.
Changing Rows per page changes the number of pages, not the number of matching checks. Sorting a table heading changes only the current page's display order and does not change any summary card.
Empty and partial-looking results
When no checks match:
- Matching rows, Up checks, and Down checks show 0.
- Avg latency and Slowest show a dash.
- The table says no checks match the filters.
- CSV export is disabled.
A dash means no latency sample is available. It does not mean zero milliseconds.
If the totals look unexpectedly small, check the applied range, retention window, status, diagnosis, and latency filters. Select Reset to compare against an unfiltered last-24-hours result.
Summary counts versus incidents
Down checks count individual failed observations. Incident counts represent confirmed outages after regional and consecutive-failure rules.
The log summary can therefore show failed checks even when no incident opened. Review Confirmation and the incident page before treating every Down row as customer-visible downtime.