Who should receive a website-down alert?
Read the guide →Guide preview
Choose a person who can acknowledge the alert and reach the right operator. A crowded recipient list is not the same as clear responsibility.
Plan delivery, backup responsibility and a useful first response.
Plan delivery, backup responsibility and a useful first response.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Choose a person who can acknowledge the alert and reach the right operator. A crowded recipient list is not the same as clear responsibility.
A backup must know when responsibility passes to them. Adding another address without an agreed handoff can leave everyone waiting.
Select a notification route around real availability and current plan conditions. More channels do not automatically mean better response.
Separate check timing, notification delay and human acknowledgement. A shorter check interval cannot remove time spent waiting for a responder.
A monitor can keep checking while nobody is available. Decide and disclose the human coverage gap instead of assuming the subscription closes it.
Classify repeated alerts before changing thresholds or disabling them. A noisy check may reflect a real intermittent failure, an unstable condition or an unsuitable notification rule.
Define the maintenance window, affected checks and person responsible for restoring normal observation. Silence during planned work is not proof of recovery.
Assign each expiry reminder to someone who can verify the current state and reach the authorized renewal owner. Receipt is not completion.
State the confirmed impact, current action and next update. Keep suspected causes and unverified recovery times out of the promise.