Docs
About our bot
You are probably here because you saw this in your server logs or in your firewall:
PulseKeeperBot/1.0 (+https://pulsekeeper.io/bot)
That is PulseKeeper, an uptime and performance monitoring service. Someone who manages the site added it to PulseKeeper so they are told when it goes down or gets slow.
What our checks do
- Website checks make a normal
GETrequest to one address and follow up to 5 redirects. They measure how long the server takes to answer and how large the HTML is. They do not download images, scripts or styles, do not run JavaScript, do not log in and do not submit forms. - API checks send the request the site owner configured (method, headers, body) to one endpoint and check the answer.
- TCP checks only open a connection to one port and close it. Nothing is sent.
- Ping checks send ICMP echo requests.
How often
Each monitor checks one address. The site owner chooses the interval (from once a minute to once an hour, depending on their plan), with a few extra checks from other locations to confirm an outage before anyone is alerted. We never send more than 30 requests a minute to one address, however many monitors point at it.
Where from
Our checks come from these addresses:
164.90.187.198(Frankfurt)137.184.30.6(New York)138.197.198.212(San Francisco)
The list is always up to date at https://pulsekeeper.io/ips. To stop blocking our checks, see allowlisting PulseKeeper.
How to stop it
The checks exist because the site owner asked for them. If you are the site owner and no longer want them, pause or delete the monitor in PulseKeeper. If you are not the owner and our checks cause a problem, write to us at info@pulsekeeper.io with your domain and we will contact the account owner.