A checkout outage can exist while the public health check stays green. That happens when the probe reaches a healthy edge or a different backend path, while the internal load balancer is failing to deliver requests to the checkout service. The useful answer is a reconstruction path: pair an external transaction check with backend delivery signals, then correlate them by request ID, zone, and time window.
Short answer: monitor the customer-visible transaction and the internal handoff separately. A TCP connection, a 200 from a shallow health endpoint, and normal process metrics do not prove that a checkout request crossed the internal load balancer and completed. Alert on the gap between those observations, and retain enough context to explain the first failed payment attempt without guessing.
How can monitoring fail to detect service outages caused by routing issues?
The page usually arrives late and looks misleading. Customer support reports that checkout spins or returns an error.…