CSV export lets you analyze retained checks in a spreadsheet, attach evidence to an internal ticket, or compare Uptime Basics observations with server logs.
Export the applied result
- Choose the date range and filters.
- Select Apply.
- Confirm the Matching rows count represents the data you want.
- Select Export CSV.
The export includes the complete applied filtered result set, not only the current table page. Changes visible in the filter form are not included until you select Apply.
The button is disabled when there are no matching rows or while another export is running.
Export size and batching
Exports are limited to 50,000 matching checks. If the result is larger, narrow the date range or add filters and try again.
The browser retrieves the export in batches of up to 500 rows and shows progress such as Exporting 2/6. Closing the page or navigating away interrupts the browser-side export.
CSV columns
The file contains:
| Column | Meaning |
|---|---|
| timestamp | Check time in ISO 8601 UTC format |
| status | up or down for the individual check |
| http_code | HTTP response code when available |
| latency_ms | Recorded request duration in milliseconds |
| failure_category | Normalized diagnosis for a failed check |
| confirmation_summary | Regional confirmation result when applicable |
| failure_reason | Customer-facing explanation of the failure |
| recommended_action | Suggested next troubleshooting step |
| error | Stored request error text when available |
| url | Monitored URL associated with the row |
An empty value means that field was not applicable or was not recorded. For example, DNS and TLS failures can have no HTTP code.
File name and order
The browser creates a file based on the monitor name, such as example-site-logs.csv. Export rows follow the applied result's server order, normally newest first.
Sorting a visible table column affects only the current page and does not reorder the CSV.
Spreadsheet safety
CSV values are quoted and embedded quotation marks are escaped. Values beginning with =, +, -, or @ receive a protective prefix so spreadsheet software does not interpret remote text as a formula.
This protection reduces formula-injection risk, but an export can still contain sensitive operational context such as:
- Monitored URLs and paths.
- Error details.
- Failure reasons.
- Infrastructure timing and availability patterns.
Review the file before sharing it and store it according to your organization's access and retention rules.
What is not exported
Detailed Logs does not return or export saved Basic Authentication passwords, authorization secrets, or custom request-header secrets.
The CSV is a downloaded copy. It is not automatically deleted when server-side raw checks later expire, when a monitor is deleted, or when the account is closed. You are responsible for copies saved to your device or other systems.
If an export does not complete
- Confirm the page is online and the signed-in session is active.
- Narrow a large range or select a smaller filtered result.
- Keep the tab open until all batches finish.
- Retry once after a temporary network failure.
- Do not repeatedly press Export while the button shows progress.
Export through the customer API
API integrations use a separate asynchronous workflow so a large CSV does not keep one request open:
- Request the job with
POST /v1/exportsand anIdempotency-Key. - Read its status from
GET /v1/exports/{exportId}. - When ready, request a five-minute private URL from
GET /v1/exports/{exportId}/download.
API export jobs support the same 30-day raw-check retention boundary and 50,000-row maximum. At most two exports can be queued or processing for one account. Generated API artifacts expire after six hours and are deleted automatically; files you download to your own device remain your responsibility.
Use the exports:create and exports:read scopes. A selected-monitor token can export only one of its explicitly permitted monitors. The API never exports saved monitor credentials or custom request-header values.