When a Cloudflare challenge or block answers the probes, a monitor shows blocked, a warning rather than an outage. Until 15:36 UTC today every scheduled round that met the challenge again started a fresh set of confirmation rounds, which was noise for the site and for our fleet. Now a monitor that is already blocked stays blocked quietly until the answer changes; the state, the alert and the panel are the same as before. The Cloudflare check tells you in advance whether a WAF treats the probes this way, and the probe IPs are public so you can allow them.
The same deploy added per-key API limits: a key can be given higher read, write or check-now limits on request, and the rate-limit headers then show that key's own numbers.