Skip to main content

Troubleshooting uptime checks

Most failures fall into a few predictable categories.

405 Method Not Allowed​

The endpoint rejected the HTTP method. Switch back to GET, or choose the method your API actually supports.

Timeout​

The server did not answer before the timeout. Increase the timeout only when the endpoint is allowed to be slow. Otherwise, investigate server load, DNS, TLS or network routing.

Status code mismatch​

The response worked technically, but the status code is outside your allowed rules. Update expected status codes only when the returned status is truly healthy for your application.

For blocked, rate-limited or intentionally protected endpoints, see Allowlisting and HTTP status codes.

Text or JSON assertion failed​

The endpoint responded, but the content did not match the expected contract. Check whether the page changed, the API schema changed or the assertion is too strict.

Regional mismatch​

If only one distant region is slow, the origin may still be healthy. If nearby regions are slow too, treat it as a stronger performance signal.