Locations and IPs.

Here is the list of our IPs so you can whitelist them if needed.

Home / Help Center / Locations

UptimeRobot uses a distributed monitoring system to minimize false-positives.

All primary checks are made from the main engines in Dallas-USA. However, once a downtime is detected, secondary requests to verify this downtime is sent from remote nodes that are located in different countries/continents.

Whitelisting

If the monitoring works well for you, there is no need to take any actions. But, if you get any false/positives, there is a strong chance that the IPs used are blocked by your hosting provider.

Please make sure that you whitelist these IPs so that any requests that UptimeRobot send are not blocked.

Locations and IPs

The main monitoring location is in Dallas-USA and there are other nodes in other countries/continents to verify down statuses.

Here are all the locations and IP networks we use:

69.162.124.224/28 (Dallas - USA)

63.143.42.240/28 (Dallas - USA)

216.245.221.80/28 (Dallas - USA)

208.115.199.16/28 (Dallas - USA)

216.144.248.16/28 (Dallas - USA)

2607:FF68:107::/48 (Dallas - USA)

Others

  • 104.131.107.63 - 2604:a880:800:10::4e6:f001 (New York - USA)
  • 122.248.234.23 (Singapore)
  • 128.199.195.156 - 2400:6180:0:d0::16:d001 (Singapore-2)
  • 138.197.150.151 - 2604:a880:cad:d0::18:f001 (Toronto-2 - Canada)
  • 139.59.173.249 - 2a03:b0c0:1:d0::22:5001 (London-2 - UK)
  • 146.185.143.14 - 2a03:b0c0:0:1010::2b:b001 (Amsterdam-2 - Netherlands)
  • 159.203.30.41 - 2604:a880:cad:d0::122:7001 (Toronto - Canada)
  • 159.89.8.111 - 2a03:b0c0:3:d0::44:f001 (Frankfurt-2 - Germany)
  • 165.227.83.148 - 2604:a880:400:d0::4f:3001 (New York-2 - USA)
  • 178.62.52.237 - 2a03:b0c0:1:d0::e54:a001 (London - UK)
  • 18.221.56.27 - 2600:1f16:775:3a01:70d6:601a:1eb5:dbb9 (Ohio - USA)
  • 167.99.209.234 - 2a03:b0c0:2:d0::fa3:e001 (Amsterdam - Netherlands)
  • 216.144.250.150 - (Dallas - USA)
  • 34.233.66.117 - 2600:1f18:179:f900:88b2:b3d:e487:e2f4 (Virginia - USA)
  • 46.101.250.135 - 2a03:b0c0:3:d0::33e:4001 (Frankfurt - Germany)
  • 46.137.190.132 (Dublin - Ireland)
  • 52.60.129.180 - 2600:1f11:56a:9000:23:651b:dac0:9be4 (remote13.uptimerobot.com) (Montreal - Canada)
  • 54.64.67.106 (Tokyo - Japan)
  • 54.67.10.127 (California - USA)
  • 54.79.28.129 (Sydney - Australia)
  • 54.94.142.218 (Sao Paulo - Brazil)
  • 52.70.84.165 (Notifications) (Virginia - USA)
  • 54.225.82.45 (Notifications) (Virginia - USA)
  • 3.21.136.87 (Ohio - USA)
  • 18.116.158.121 (Ohio - USA)
  • 18.223.50.16 (Ohio - USA)
  • 54.224.73.211 (Virginia - USA)
  • 35.170.215.196 (Virginia - USA)
  • 35.153.243.148 (Virginia - USA)
  • 54.241.175.147 (California - USA)

And, here they are in .txt format in case you prefer to whitelist them in the firewall rules automatically:

P.S. Remote nodes currently have dynamic IPv6 addresses and they are not mentioned for this reason.