You've probably come across this URL because you're seeing HTTP requests from an HTTP User-Agent like:
HeiiOnCall_UptimeCheckBot/2.0 ({{INTERNAL_STRING}}) +https://heiioncall.com/uptime_check_bot
This is Heii On-Call's client for monitoring the availability and uptime of your HTTP endpoints.
If you are getting requests from this client, it is likely that someone in your organization set up one or more of Heii On-Call's Outbound Probe Triggers to automatically monitor the availability and uptime of your website, health check, or other API endpoints.
You might also see requests from this client if your hosting provider uses Heii On-Call. In this case, these uptime checks will be configured by your hosting provider to monitor their platform and provide real-time and historical visibility to their infrastructure teams.
Per the RFC 9309 "Robots Exclusion Protocol", you may disallow the UptimeCheckBot from making queries to your server by placing a plaintext file at /robots.txt
.
Per RFC 9309, we MAY
cache this file for up to 24 hours. (Of course, even if blocked, we MAY
still make occasional GET /robots.txt
queries to see if the file has changed.)
To block our UptimeCheckBot, add the following to your /robots.txt
file:
User-agent: HeiiOnCall_UptimeCheckBot
Disallow: /
Note that once this change is detected, all of your organization's Outbound Probe triggers will transition to alerting
, paging the person on-call. Be sure to communicate this change to any engineering and operations teams that may be using Heii On-Call to monitor your website or API endpoint availability and uptime.
Our /robots.txt
parser ignores any Allow:
lines. Our parser only looks at Disallow: /
lines which are for the root path /
. Our parser does not follow redirects for /robots.txt
.