Added support for targeting probes with state level accuracy
We have added optional input
StateCode parameter to those methods:
Currently only probes located in the USA can be targeted on state level. The API response will also contain
StateCode (e.g. VA) and also
State (e.g. Virginia) if you request
Added new limits on the number of probes you can request test from To avoid abuse we have added limits to how many probes you can request results at the same time in 1 API call. This is controlled by the probeLimit parameter which is required.
Here are the maximum values allowed for different tests.
PING – 100
DIG – 100
TRACEROUTE – 100
PAGELOAD – 20
HTTPGET – 20
If you require those limits to be lifted, please contact us.
Added web reputation services for HTTP tests
To avoid abuse and protect the probes from accessing risky content, we have added white and black lists that will be checked for all HTTP tests (e.g. HTTP GET or Page load). Following errors can happen>
StatusDescription: Destination blocked Message: “This URL destination has been marked as risky by our web classification engine. We are unable to test this URL. ”
StatusDescription: Destination not classified Message: “This URL destination has not been classified by our web classification engine. We are unable to test this URL at this time. Please contact support to whitelist this URL”