Checks Around Incident provides check-level evidence close to an incident without loading a large table every time the Incident Details page opens.
Load the section
Expand Checks Around Incident near the bottom of the page. The data is fetched only when you open the section, which keeps the initial incident view faster.
The table can include:
| Column | Meaning |
|---|---|
| Time | When the check ran in your selected account time zone. |
| Status | Whether the check was Up or Down. |
| HTTP | Returned HTTP status, when a response was received. |
| Latency | Total recorded response time. |
| Diagnosis | Normalized category and reason based on the check evidence. |
| Confirmation | Available multi-region confirmation result. |
| Error | Request error when the check did not produce a normal HTTP response. |
A dash means that field was not available. For example, DNS, TCP, TLS, and timeout failures usually do not have an HTTP status.
Use the checks to establish sequence
Compare the rows to answer:
- What failed immediately before the incident opened?
- Did the failure repeat with the same diagnosis?
- Was the problem reproduced by regional confirmation?
- Did successful and failed checks alternate?
- Which successful result appeared near recovery?
Use the incident start time as the confirmed transition, not necessarily the first unsuccessful attempt. Availability incidents require consecutive region-confirmed failures before opening.
Understand the bounded sample
This section loads a bounded sample from around the incident window. For a long incident, it keeps evidence near the beginning and end instead of retrieving every check from the middle.
The sample is designed for quick incident context. It must not be used to count every check or calculate exact downtime on its own.
When to use Detailed Logs
Open Detailed Logs when you need:
- Every retained check in a chosen 24-hour, 7-day, 30-day, or custom range.
- Up-only or Down-only filtering.
- HTTP, diagnosis, latency, or text filters.
- Pagination and larger page sizes.
- CSV export.
Raw checks are retained for 30 days. Older incidents can remain available after their nearby raw checks have expired.
If the section is empty
An empty or limited section can mean the raw checks have expired, the incident is old, no supporting records were available, or the request could not be loaded. Retry once, then use Detailed Logs for a period still within retention.