Common causes are a single network hiccup between the check location and the server, timeouts set too short, firewalls, CDNs or bot protection blocking the monitor, rate limits, and content checks on text that changes.
False positives cost more than the interruption: they teach people to doubt alerts, which slows the response to real ones (alert fatigue). A false negative, a real outage that is never alerted, is the opposite failure, and tuning hard against one can cause the other.
Confirming a failure with a second check removes most network blips. Allowing the monitor’s IP addresses or user agent through firewalls removes blocks.