Source

Alerting, escalation & on-call — found from sitemap — updown.io

Checked for updown.io on 1 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:097ec856d444ab5d02715a8535ad0912a0085a1c65c9ab195a0e829d8c68d921
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Downtime confirmation checks Report an error

“We verify downtimes two additional times before notifying you, from at least one different location (so three down checks required in total).”
Verification check speed Report an error

“we perform these two verification checks twice as fast as your configured interval.”
Short downtime not notified Report an error

“This means that any downtime shorter than your check interval (shorter than 1min in this example) will not be notified.”
Downtime notification guarantee Report an error

“And any downtime longer than your check interval * 1.5 (longer than 1min30s in this example) is guaranteed to be notified.”
Recovery checks Report an error

“we'll require three up check to close the downtime. Like for downtime confirmation, these checks will run twice as fast and from at least two different locations.”
Reminder alerts Report an error

“If you check stays down for a long time, we also send "still down" reminder alerts (except by SMS to avoid the extra cost). The first reminder is sent after 60 down checks”
Reminder interval Report an error

“After the first reminder, each following reminder is sent after a polynomially increasing time delay (e.g. 1h, 2h, 4h, 8h, 16h...)”
Reminder configurable Report an error

“This is (in our opinion) a great default for most situation and cannot be configured.”