Pause & disable
Two ways to stop a monitor from running without deleting it. Pick the one that matches your situation.
Pause (temporary, auto-resume)
Use Pause for… when you're doing planned maintenance and want the monitor to stop checking for a specific window. Click the dropdown on the monitor's row, pick 1 hour / 4 hours / 24 hours / 7 days, and the agent skips it until the timer elapses. No manual unpause needed.
While paused: no HTTP / SSL / ping / sitemap check fires, no rows are written to the results table, no alerts can be triggered. The monitor is effectively invisible to the agent.
Disable (indefinite)
Use the Active / Disabled toggle when you want to stop a monitor without a fixed end-date. Click again to re-enable.
Disabled monitors still count toward your plan's monitor limit, but the agent skips them — same as paused.
Automatic pausing
ViewPeek pauses a monitor on its own in two situations. Both send you a single "we paused this for you" email, and both are undone by clicking Resume on the monitor.
Too many alerts at once
If a single monitor fires 5+ alert emails within 60 minutes, ViewPeek auto-pauses it for 1 hour. This catches misconfigured thresholds or downstream blips before they fill your inbox.
You can also widen the Resend alert interval on the monitor to reduce repeat alerts going forward.
Alerting non-stop for too long
If a monitor has been alerting continuously for 7 days without the target ever recovering, ViewPeek auto-pauses it for 30 days. A monitor in this state is almost always pointed at something retired or permanently moved, and it keeps mailing you a few hundred times a month for no benefit — which damages our ability to deliver mail to your address at all.
"Continuously" means the alert was never resolved. A site that goes down and comes back, even daily, resets the clock and is never auto-paused this way — only an unbroken 7-day failure counts.
This applies to uptime and ping monitors only. SSL monitors are never paused this way: an SSL monitor warns you every day for the 30 days before a certificate expires, which is exactly what it's supposed to do, and pausing it would silence the warning right before it matters.
If the target is retired, delete the monitor. If you've fixed it, click Resume and monitoring restarts immediately.
Pause vs disable
| Pause | Disable | |
|---|---|---|
| Duration | Time-bounded (auto-resumes) | Indefinite (until you re-enable) |
| UI control | "Pause for…" dropdown | "Active / Disabled" toggle |
| Best for | Planned maintenance, brief noise | Long-term retirement |
| Counts toward plan limit | Yes | Yes |
Tips
- If you want both controls active at once (e.g. disabled now AND was previously paused for 4 hours), they coexist — the agent skips if either says don't run.
- To stop alerts permanently, delete the monitor instead.
- For a planned deploy where you want the data preserved but alerts muted, use a maintenance window instead of pause — checks keep recording so your uptime stays accurate.
Next steps
- Schedule a maintenance window for planned work — alerts mute, checks keep recording.
- Route alerts to Slack so a paused monitor is one click away in your team chat.
- Widen the resend interval on chatty monitors to reduce repeat alerts.