Uptime Basics keeps different kinds of monitoring data for different periods. Raw troubleshooting data is retained for a shorter period, while compact summaries and incident history remain available longer.
Retention summary
| Data | Retention | What it is used for |
|---|---|---|
| Raw check logs | 30 days | Individual timestamps, status codes, response times, and diagnoses in Detailed Logs |
| Alert history | 14 days | Recent notification queue, delivery, failure, and suppression records |
| Incident history | Life of the monitor | Confirmed availability and performance incidents, including retained incident diagnostics |
| Aggregated rollups | Up to 400 days | Long-range availability and response-time views, including the one-year range |
| Deleted monitor recovery snapshot | 30 days | Restores an accidentally deleted monitor in a paused state |
| Monitor configuration revisions | Up to 30 days or 100 revisions | Supports audited administrator rollback of recent setting changes |
| Active or archived monitor configuration | Until the monitor or account is permanently deleted | URL, interval, timeout, request settings, alert choices, and optional feature settings |
| Free service-status checks | 24 hours | Raw checks used to prepare Recent History on Uptime Basics free service pages |
These are customer monitoring-data periods. Billing, invoice, consent, security-audit, fraud-prevention, and legal records follow separate requirements described in the Privacy Policy.
Why data has different retention periods
A one-minute monitor can create more than 43,000 raw checks in a month. Keeping every raw record indefinitely would make long-range pages slower and create unnecessary storage and processing overhead.
Rollups combine checks into time buckets. They preserve the availability and response-time information needed for charts without loading every individual record. The one-year interface reads these compact summaries rather than all raw checks.
Retention is measured from the time a record is created. A record that has reached the end of its retention period is no longer part of the supported customer history. Background storage deletion can complete asynchronously.
What happens when a monitor is paused
Pausing stops new checks. Existing data continues to age according to the normal retention periods. Incident history remains associated with the monitor while the monitor exists.
What happens when a monitor is archived
The monitor configuration is preserved as part of the plan-change workflow. Raw checks, alert history, and rollups continue to expire normally. Existing incidents remain associated with the archived monitor. Archiving does not reset or extend any retention period.
What happens when a subscription ends
Monitoring and alerts stop when paid service ends. Monitor configuration remains associated with the account unless the monitor or account is deleted. Existing raw checks, alerts, and rollups continue to age under their normal retention periods, while incident history remains for the monitor's lifetime.
What happens when a monitor is deleted
Deleting a monitor stops checks immediately and places a recovery snapshot in Recently deleted for 30 days. Its public status page is disabled and its slug remains reserved during that period. The monitor can be restored paused if the account still has capacity and the target remains allowed.
Raw checks, alert history, and rollups continue to age normally during the recovery period. Permanent background cleanup begins after 30 days or when the account owner selects Delete permanently.
What happens when an account is deleted
Account deletion is support-assisted. After the 30-day waiting period completes, monitor configuration and operational monitoring data are permanently deleted. Limited billing, invoice, consent, security, fraud-prevention, and legal records may be retained where required.
Free service-status pages
The free pages under the Public Pages directory use a separate 24-hour raw-check window. Their Recent History presentation may sample that data at a wider display interval to keep the page concise. This does not change paid-monitor retention.