Why was my check blocked?

Symptom

A monitor shows a blocked destination and never runs a normal check.

Most likely causes

• The hostname resolves to a private IP address.
• The URL points to localhost or a loopback address.
• A redirect leads to a restricted destination.
• The port or protocol is not supported.

How to confirm

Resolve the hostname from a public network and confirm it returns a public address. Follow any redirects to their final destination.

Resolution

• Use a publicly reachable HTTPS endpoint.
• Remove redirects to private destinations.
• Confirm DNS resolves publicly.

What Fajita records

The result is recorded as blocked and is excluded from uptime. See Monitoring destinations.

When to contact support

If the endpoint is genuinely public and still blocked, contact support with the URL. Do not include secrets.