---
title: Reset a monitor's history without recreating it
description: Starting a monitor's statistics over used to mean cloning it and deleting the original, which gave you a new id, dropped the tags and broke every link to the…
canonical: https://watchfor.io/changelog/2026-09-04-reset-monitor-history
---

[All updates](/changelog/page/5#2026-09-04-reset-monitor-history) ✨ New Sep 4, 2026 · v 6.7.3

# Reset a monitor's history without recreating it

Starting a monitor's statistics over used to mean cloning it and deleting the original, which gave you a new id, dropped the tags and broke every link to the old one. Reset history, in the monitor's menu, now deletes everything the monitor has recorded (checks, incidents with their timelines, notes, post-mortems and status-page incidents) and uptime starts again from that moment, while the monitor keeps its id, settings, alert rules, tags, locations and status-page components. It cannot be undone, so you type the monitor's name to confirm. Owners and admins; also in the API.

You type the monitor's name to confirm, because a reset can't be undone.

## Why

Some monitors need a clean start: you rebuilt the service behind one, it spent a week pointed at a staging server, or a load test filled it with incidents that mean nothing now. Cloning and deleting gave you a fresh monitor but a new id, so every link, status page and API script that used the old one broke.

## What a reset deletes

- every check and its latency history

- incidents, with their timelines and notification history

- internal notes and post-mortems

- the incidents that were published to status pages

## What it keeps

The monitor's id, settings, alert rules, tags, locations and status-page components. Checks keep running: the monitor shows Unknown until the next result arrives, and its uptime says since reset until it has a full day of data.

## Example

You move "Checkout API" to a new cluster after a migration week full of incidents. Choose Reset history , type Checkout API to confirm, and uptime is counted from that moment. Your status page, dashboards and scripts still point at the same monitor.

## Where

On the monitor page, ⋯ → Reset history , for owners and admins. A reset can't be undone. Through the API it is POST /v1/monitors/{id}/reset ([docs](/docs/api/monitors#reset-history)).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-04-reset-monitor-history · Site guide: https://watchfor.io/llms.txt
