Pause a PD Uptime & Status monitor when checks should temporarily stop during planned work. This keeps the monitor and its history, unlike removing it. Pausing changes monitoring behaviour in Blesta; it does not itself unpublish a public status entry or detach the customer.

Pause the intended monitor

1. Open PD Modules → Uptime → Monitors.
2. Identify the exact label, address and customer association.
3. Choose that row’s Pause action.
4. Check that its state is Paused and the action has changed to Resume.

Paused monitors are excluded from scheduled checks and Check everything now. They do not generate new down or recovery alerts while skipped. A previous result or timestamp is historical, not a current successful check during the pause.

Keep visibility separate

If the monitor is published on the Pro public status page, Pause does not remove its publication flag. Use Unpublish when it should leave that page. Customer association is another separate choice: unlinking the service does not remove public status publication either.

An already open incident is not automatically closed just because the monitor is paused. Do not use Pause as evidence that the underlying outage has been resolved.

Resume and verify a fresh result

After the work, choose Resume on the same monitor and check its result after the next eligible round. Resume resets the monitor to pending with its failure count cleared; it does not immediately declare it healthy.

Check the current timestamp, target response and incident history. A pause/resume sequence can change normal transition-alert behaviour, so do not rely on a recovery email alone to confirm that checks restarted. If there is no fresh result, review the checking allowance and cron before repeatedly clicking actions. Avoid Remove for temporary maintenance because removal also discards the monitor’s history.

See the PD Uptime & Status Blesta guide for related tasks, or explore PD Uptime & Status.