Node.js Monitoring Fails to Detect Internal Service Outages Regional Probes Beat Endpoint Checks
Short answer: endpoint-only monitoring misses internal load balancer outages because it checks the edge, not every region-to-backend path; for a gaming cohort rollout, use regional probes and cohort-aware rollback checks alongside the endpoint check.
An internal load balancer can be down while the public endpoint still looks healthy. The usual reason is not that monitoring is broken; it is that the check observes the wrong boundary. For a gaming experiment, I would choose regional probes plus cohort-aware rollback checks over endpoint-only uptime checks. The endpoint check remains useful, but it cannot prove that traffic is reaching the intended backend pool.
The practical rule is simple: keep the endpoint check for fast detection, add checks from the regions that matter to players, and make the rollback decision depend on a second signal that exercises the experiment path.…