Monitors & detections
Give each check the right amount of time
Understand the timeout budget, redirects and public target requirements.
Reviewed
Choose the timeout
In HTTP settings, Timeout (seconds) accepts values from 0.1 to 60. The budget covers the whole check, including DNS lookup, redirects and any response content read for validation.
For example, a 10-second timeout is one budget for the check. Each redirect does not receive another 10 seconds. Choose a timeout that fits your endpoint’s expected behavior.
Follow the path deliberately
Follow redirects permits up to five redirects. When it is off, the monitor evaluates the original response against Healthy HTTP codes. The default 200-399 range includes redirect responses.
Protected requests and methods other than GET or HEAD do not follow redirects to another origin. Update the monitor to the intended final URL rather than relying on a cross-origin redirect.
Only public addresses are checked
Targets and redirect destinations must resolve to permitted public addresses. Localhost, private-network addresses and infrastructure metadata endpoints are not supported by these public HTTP monitors.
If a check fails, inspect its error and response code before extending the timeout. A blocked destination or unexpected response will not be corrected by waiting longer.