About our health check requests

If you found Agent Pong/0.1 (+https://agentpong.com/bot) in your logs, this page explains what sent the request and who controls it.

What it is

Agent Pong hosts status pages for software teams. A team can set up health checks: requests to URLs it chooses, whose results keep its status page current. Each request carries the user agent Agent Pong/0.1 (+https://agentpong.com/bot).

The checker requests only the configured URL, plus any redirects it is told to follow. It doesn’t crawl, follow links on the page or run scripts. It reads at most the first 256 KB of a response.

The “Check an endpoint” form on our homepage uses the same user agent. Each use sends one GET request, and the form is limited to six checks a minute.

How often it runs

  • Each health check runs on its own schedule, at most once a minute.
  • When a check fails, it is checked again about 15 seconds later before the failure counts.
  • Requests time out after 1 to 30 seconds (10 by default) and follow at most five redirects.

Where requests come from

There is no fixed list of IP addresses that requests come from, so identify the checker by its user agent. Requests to private, loopback and internal addresses are refused.

Who controls it

The team that created the health check chooses the URL, method, headers and schedule. Our terms allow teams to check only endpoints they own or are authorised to test.

Contact

If you think a health check is aimed at your site without permission, or it causes problems, contact us with the URL being requested and a timestamp from your logs. We can pause health checks that break our terms.