Match the original failure
Read the original alert before choosing a recovery check. If a public page timed out, confirm that same address now responds. If a keyword disappeared, check that the expected content returned. A passing homepage does not resolve a failed booking path. Keep the original monitor condition intact while checking recovery so a relaxed threshold is not mistaken for a repaired service.
Check the reader task separately
Ask whether the affected customer action now works, using an authorized safe method. A basic external HTTP monitor does not prove a form delivers email or a payment settles correctly. Avoid making a real purchase merely to clear an incident note. Where an end-to-end test would create records, charges or messages, follow the system owner’s approved testing procedure instead of improvising in production.
Look for stability without promises
One passing response can occur during an intermittent incident. Inspect subsequent observations and other available evidence before writing a confident closure. The appropriate observation period depends on the failure pattern and business consequence; there is no universal number of green checks that certifies recovery. If the symptom returns, preserve the earlier recovery interval rather than rewriting the history into a single uninterrupted outage.
Tell the right people
Send a concise update to the people who received the incident notification, stating what has recovered and what remains uncertain. Update a public status message only within your publication authority. Record the final check time and time zone, plus any residual customer action. Finally, return temporary alert routing or maintenance changes to their intended configuration so the next genuine failure can still reach its owner. Preserve any remaining exception in the closure note for the next responder.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- UptimeRobot: website monitoring — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26
- UptimeRobot: keyword monitoring — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26