The target rate-limited our checks. Either the interval is too aggressive for this endpoint, or a shared rate limit is being hit by other traffic.
The target answered, so this is reported as a failed check, not downtime: the alert names the reason, the uptime percentage is untouched, and a recovery notice follows when the check passes again.
Caught by: httpkeywordapi monitors. Read about the api monitoring feature.
Ten monitors free, no card, no time limit. Every incident names the failure.
Start monitoring freeOther causes