The majority-of-locations rule is the part I'd care about most, but our worst outage wasn't a clean down at all. On our iGaming job board, bot traffic hammering heavy search queries tied up every worker, while /healthz kept answering 200 in a few milliseconds and real job pages took 30+ seconds or timed out. External checks stayed green for hours. We ended up pointing the monitor at an actual search page with a timeout and a text match instead of the health endpoint. Can a Pulseping HTTP check fail on a response-time threshold or a missing string in the body, or is it status code only?