Skip to content

How do I allow our checks in a firewall?

Not our customer, and wondering why we visit? See Why is Uptime Gorilla checking my site?

A firewall, a security plugin or a rate limit can stop our checks before they reach your website. The monitor's page then says Our check was blocked by a firewall, Access refused (403) or Too many requests (429), and the monitor needs attention. These results count as up in the uptime, never as down, but while they last nobody can tell whether the website is up. Allow our checking servers, and the checks reach it again.

Our checking servers

Every check comes from one of these servers, by its address or by its name:

Place Name IPv4 IPv6
Amsterdam, Netherlands ug-probe-ams1.uptimegorilla.com 172.233.49.148 2600:3c0e::f03c:94ff:fe2a:57e0
Newark, United States ug-probe-ewr1.uptimegorilla.com 23.92.16.239 2600:3c03::2000:d3ff:fe72:c821
Singapore ug-probe-sin1.uptimegorilla.com 172.104.63.131 2400:8901::2000:29ff:fe86:999d
São Paulo, Brazil ug-probe-gru1.uptimegorilla.com 172.233.11.136 2600:3c0d::2000:b1ff:fe8c:83b8
Helsinki, Finland (screenshots for alert emails) ug-shots-hel1 62.238.32.18 2a01:4f9:c015:870::1

Every check also says who it is: its user agent contains UptimeGorilla. The Helsinki server only opens a page for the screenshots in a Down or Up again email, with a browser whose user agent also contains UptimeGorilla. A ping monitor's ping requests come from the same addresses.

Allow both addresses of each server, IPv4 and IPv6. Your website may be reached over either.

Copy the list

Every address, one per line, ready to paste into a firewall's allow list:

172.233.49.148
2600:3c0e::f03c:94ff:fe2a:57e0
23.92.16.239
2600:3c03::2000:d3ff:fe72:c821
172.104.63.131
2400:8901::2000:29ff:fe86:999d
172.233.11.136
2600:3c0d::2000:b1ff:fe8c:83b8
62.238.32.18
2a01:4f9:c015:870::1

The same on one line, for a field that takes addresses separated by commas:

172.233.49.148, 2600:3c0e::f03c:94ff:fe2a:57e0, 23.92.16.239, 2600:3c03::2000:d3ff:fe72:c821, 172.104.63.131, 2400:8901::2000:29ff:fe86:999d, 172.233.11.136, 2600:3c0d::2000:b1ff:fe8c:83b8, 62.238.32.18, 2a01:4f9:c015:870::1

As files, for a script or a firewall that reads a list from an address: ips.txt (all), ips-v4.txt and ips-v6.txt, plain text files with one address per line. When we add a checking server, its addresses are on this list before it checks anything.

When the monitor names the firewall

The monitor's What our checks saw says what each place got and, after a firewall's page, What you can try gives the steps. When the page that stopped it shows which firewall sent it, the monitor names that firewall, for example Probably Kinsta's Bot protection., with its own steps, the same as below; otherwise it says Probably a firewall or a security plugin in front of the website. It is the likely cause, not a certainty: if the steps do not help, ask your host which firewall answers.

Allow our user agent first where the firewall offers it, then our addresses if the checks are still stopped. Every check's user agent is Mozilla/5.0 (compatible; UptimeGorilla/0.1; +https://uptimegorilla.com); a rule that looks for UptimeGorilla in it matches every version.

Kinsta

Kinsta's Bot protection can stop our checks with a "Just a moment..." page.

  1. In MyKinsta, open the site, then Bot protection.
  2. Add an Always allow exception for the user agent UptimeGorilla. If MyKinsta wants the whole user agent, give the one above.
  3. If our checks are still stopped, add each of our checking servers' addresses above as an Always allow exception too.
  4. Still stopped: ask Kinsta's support. Its platform's own security comes before your exceptions.

Cloudflare

Add a custom rule that skips the security checks for our checking servers' addresses (under Security, then Security rules or WAF, depending on your dashboard), or add each address as an IP Access Rule with the action Allow. Allow them by address, not by our user agent, which anyone can copy.

If Bot Fight Mode is on, no rule can skip it: switch it off under Security, then Bots, or our checks stay stopped.

Wordfence

In WordPress, open Wordfence, then Firewall, then All Firewall Options, and add our checking servers' addresses to the allowlisted IP addresses.

Sucuri

In the Sucuri Firewall dashboard, open Settings, then Access Control, and add our checking servers' addresses to the allowed addresses.

A rate limit

Leave our addresses out of the limit. Our checks are few, far below any normal limit; you can also check less often.

Another firewall

  • A security plugin: add the addresses to its list of allowed IP addresses.
  • The server's own firewall or your host's: allow web traffic (ports 80 and 443) from the addresses.

Check that it works

Open the monitor's page. The next result after your change should be Up, or a result that says what is wrong with the website itself.

When only a firewall answers our checks for 2 hours while a monitor is down, we end that outage, as we can no longer tell whether the website works, and send Can no longer check (alerts).