In addition to the IPs being currently used, we’ll be starting to use (effective by 2015-10-12) a set of new IPs parallel to the new machines to be joined to the system. Here they are:
- IP Block: 22.214.171.124/28
- Or, the IPs that will be used:
- 126.96.36.199 – engine5.uptimerobot.com
- 188.8.131.52 – engine6.uptimerobot.com
- 184.108.40.206 – engine7.uptimerobot.com
- 220.127.116.11 – engine8.uptimerobot.com
- 18.104.22.168 – engine9.uptimerobot.com
- 22.214.171.124 – engine10.uptimerobot.com
- 126.96.36.199 – engine11.uptimerobot.com
- 188.8.131.52 – engine12.uptimerobot.com
- 184.108.40.206 – for future use
- 220.127.116.11 – for future use
- 18.104.22.168 – for future use
- 22.214.171.124 – for future use
- 126.96.36.199 – for future use
If your monitors are behind a firewall and had needed to whitelist Uptime Robot’s current IPs, please make sure that you whitelist these IPs as well for the monitoring to function as expected.
14 replies on “New IPs For Monitoring (Have a Firewall? Make Sure You Whitelist Them..)”
Are you planning to add these ips to https://uptimerobot.com/inc/files/ips/IPv4.txt ?
Sorry for the delay.. They are added.
Cheers for the up-to-date. My scripts might have triggered a ban for your hosts due to the new hosts. Since then added a cron to fetch IPv4.txt.
Is it possible for you to publish an ipv4-and-ipv6.txt file or should i concat myself?
Just published an IPv4 and IPv6 combined file at: http://uptimerobot.com/locations 🙂
Some of our monitors which are being checked from 188.8.131.52 don’t seem to be working.
We haven’t had any checks all day today (so far). We’ve even paused and restarted the monitors several times and have waited a couple of hours, but nothing yet. The monitors are set to run every 5 minutes, but they have not worked since yesterday.
The requests can be coming from the new IPs. Please let us (firstname.lastname@example.org) know if the issue still exists.
Your IP block appears to be incorrect (only including .224->.228). To include the full IP range, shouldn’t it be: IP Block: 184.108.40.206/38
The info looks correct. Here are more details on displaying IP blocks :https://www.mediawiki.org/wiki/Help:Range_blocks .
At least for what is showing now on this page, the /28 subnet appears to correctly cover IP Address from .225 to .238, I used https://www.calculator.net/ip-subnet-calculator.html?cclass=any&csubnet=28&cip=220.127.116.11&ctype=ipv4&printit=0&x=67&y=18 to confirm.
Just started with the service – looks really good so far. I wrote a quick Regular Expression for the IP address for Google Analytics and I thought it might be helpful to share
Hope it’s useful (and correct!)
Sorry! Just noticed I didn’t escape some of the periods
Any chance of versions of these address lists which list the block forms? At least two of the IPv4 ranges (as of Aug-2016) are small defined subnets, and I assume the IPv6 addresses are in two common subnets. If we could have some sort of CIDR forms perhaps in a -blocks variant that would make setting up firewall rules simpler (and shorter):
We’ll definitely be adding the blocks very soon.
Would it be possible to subscribe to the IP list so if it changes (or there are going to be changes) I can receive a notification?