Common Issues

Solutions to frequently encountered issues.

Check shows "Unknown" status

A check starts with an unknown status and will update to up or down after the first execution cycle. If it stays unknown:

• Ensure your team has a positive credit balance.
• Ensure the check is active (not paused).
• Check that at least one agent is assigned to the check.

False "Down" alerts

If a check flickers between up and down:

• Whitelist agent IPs — your firewall or WAF may be blocking agent requests. See How to Whitelist Our Agents.
• Increase the interval — if your server rate-limits requests, a 30-second interval may trigger throttling.
• Check expected status — if your server redirects (301/302), make sure the expected status matches.

Credits depleting faster than expected

Credit usage depends on: number of active checks × (60 / interval_seconds). To reduce consumption:

• Increase check intervals (60s → 300s reduces consumption by 5×).
• Pause checks you don't actively need.
• Remove duplicate checks.

Notifications not received

• Verify the webhook channel is enabled (not disabled).
• Use the Test button on the notification channel to verify the webhook URL is valid.
• Ensure you (or the webhook) is assigned as a recipient on the specific check.
• Check your Slack/Teams channel — the notification may have been delivered to a different channel than expected.

Cannot create checks (403 Forbidden)

Only team admins can create, edit and delete checks. If you have the viewer role, ask a team admin to upgrade your permissions.