What the checker is
Monitive is an uptime monitoring service. Its checker runs HTTP, TCP and ping (ICMP) checks against targets that Monitive customers configure. It sends them from 21 probe addresses.
Private, reserved and loopback addresses can't be monitored.
User-Agent
HTTP checks send this User-Agent header:
Monitive/2.0 (+https://monitive.com/bot) The product token is Monitive. Anyone can copy a User-Agent, so identify Monitive by the IP addresses below or by the request signature, not by this header alone.
What it requests and how often
- Each monitor checks its target once a minute, spread across the minute rather than at the top of it.
- A failed check is re-checked from 2 other regions before the monitor changes state, which means up to 2 extra requests.
- A monitor that stays down for 10 minutes backs off from one check a minute to one every 5 minutes.
- A
429 Too Many Requestsresponse marks the monitor down straight away, with no confirmation checks from other regions, so a rate-limited target gets no extra requests. - HTTP checks use the method the customer chose (
GET,POST,PUT,DELETE,PATCHorOPTIONS, neverHEAD), with the customer's headers and body, and a timeout of 1–30 seconds (30 by default). - The same request goes out when a monitor is created, on every scheduled check, on a manual Run test, and on the confirmation checks.
Request signing
HTTP check requests are signed with Web Bot Auth, which uses HTTP Message Signatures (RFC 9421).
A signed request carries Signature-Input, Signature and Signature-Agent. For Monitive, Signature-Agent is "https://api.monitive.com". That host publishes Monitive's public keys in its HTTP Message Signatures key directory. To confirm a request came from Monitive, verify its signature against those keys.
IP addresses
Monitive's probes send checks from these 21 IPv4 addresses:
- 37.143.130.229
- 45.154.205.250
- 89.163.210.254
- 103.25.56.101
- 103.75.118.67
- 103.106.231.119
- 104.168.10.110
- 104.168.22.69
- 107.172.29.151
- 107.173.146.44
- 107.175.1.49
- 147.78.0.156
- 159.65.153.135
- 163.47.21.159
- 167.150.100.159
- 185.123.101.69
- 185.186.79.130
- 185.192.124.253
- 192.3.81.235
- 192.119.89.29
- 198.23.228.179
The list changes when a probe is added or retired. For automation, fetch the current list from https://api.monitive.com/locations: plain text, one IPv4 address per line.
Allow Monitive through Cloudflare
Skip only the one feature that usually blocks a monitoring tool:
- Create a WAF custom rule named, for example,
Allow Monitive. -
Choose Edit expression and paste the expression:
(ip.src in {37.143.130.229 45.154.205.250 89.163.210.254 103.25.56.101 103.75.118.67 103.106.231.119 104.168.10.110 104.168.22.69 107.172.29.151 107.173.146.44 107.175.1.49 147.78.0.156 159.65.153.135 163.47.21.159 167.150.100.159 185.123.101.69 185.186.79.130 185.192.124.253 192.3.81.235 192.119.89.29 198.23.228.179}) - For the action, choose Skip, then select All Super Bot Fight Mode rules only.
- Deploy the rule and place it first in the custom rules list, so no earlier custom rule blocks the request before this one runs.
The rule matches on IP addresses, not the User-Agent, because a User-Agent can be spoofed.
Skip phases are selected one at a time. Only if the zone's Security Events show that a different rule blocked a Monitive address, also select the one matching option: All remaining custom rules, All rate limiting rules or All managed rules. Don't select options you don't need, because each one turns off that protection for these addresses.
Bot Fight Mode on the Free plan can't be skipped by a WAF custom rule.
Other firewalls
Allow inbound traffic from these addresses to the ports your monitors check. Ping monitors also need ICMP echo requests allowed.
37.143.130.229
45.154.205.250
89.163.210.254
103.25.56.101
103.75.118.67
103.106.231.119
104.168.10.110
104.168.22.69
107.172.29.151
107.173.146.44
107.175.1.49
147.78.0.156
159.65.153.135
163.47.21.159
167.150.100.159
185.123.101.69
185.186.79.130
185.192.124.253
192.3.81.235
192.119.89.29
198.23.228.179 robots.txt
To address the checker in robots.txt, use the product token Monitive:
User-agent: Monitive
Allow: / To stop Monitive checking your site altogether, email hello@monitive.com to opt out. Opted-out domains are blocked from being monitored.
Report abuse
Email hello@monitive.com with the target URL or domain, the source IP address, and the time of the requests, including the time zone.