For service operators
Seen our probe
in your logs?
Here is what CheckUpstream requests, what a response tells us, and how to ask us to stop.
The request, identified.
User-Agent
checkupstream-probe/1.0 (+https://checkupstream.com/probe)- Method
- GET or HEAD, as configured for the endpoint
- Schedule
- Every 15 minutes per target
About 96 scheduled checks per target each day - Timeout
- 10 seconds by default
- Request data
- No credentials or request body
- Redirects
- Not followed
We check configured endpoints, not links discovered by crawling. A vendor can have more than one target. The schedule describes this contract probe, not every monitoring source CheckUpstream uses.
What the response tells us
Each target defines the status codes we expect and, where configured, a response-body marker. A documented authentication error can pass that check: the endpoint answered as expected without a customer account.
A passing check does not prove the product works. A failed check alone does not prove that your customers are affected.
Rate limits are inconclusive
HTTP 429 means the probe was throttled. It counts as neither reachable nor unreachable in our front door check counts.
A continuously failing contract is treated as stale after 24 hours. Its later failures are recorded as inconclusive while the configuration needs review.
How we qualify measurements