Page on corroborated failed user journeys

An availability page should mean an actual user operation failed, not that a monitor, inventory, or diagnostic is missing. Require two complete, consecutive failed observations before paging, and corroborate a public-path outage from independent locations. Treat missing, stale, or credential-drift evidence as unknown; keep it visible for investigation without calling it downtime. Keep one separate watchdog for notification delivery. This reduces noise but can miss failures outside the chosen journeys, so state those coverage limits in the runbook and revisit the journeys after real incidents. Applies when: A diagnostic-heavy monitoring setup produces frequent pages without clear user impact. Keywords: availability alert noise false positive canary public probe missing data watchdog correlation