Home » Announcements » New IPs For Monitoring (Have a Firewall? Make Sure You Whitelist Them..)

New IPs For Monitoring (Have a Firewall? Make Sure You Whitelist Them..).

Written by Tomas Koprusak 135 words | 1 min read Updated Nov 13, 2025

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: 69.162.124.224/28
Or, the IPs that will be used:
- 69.162.124.226 – engine5.uptimerobot.com
- 69.162.124.227 – engine6.uptimerobot.com
- 69.162.124.228 – engine7.uptimerobot.com
- 69.162.124.229 – engine8.uptimerobot.com
- 69.162.124.230 – engine9.uptimerobot.com
- 69.162.124.231 – engine10.uptimerobot.com
- 69.162.124.232 – engine11.uptimerobot.com
- 69.162.124.233 – engine12.uptimerobot.com
- 69.162.124.234 – for future use
- 69.162.124.235 – for future use
- 69.162.124.236 – for future use
- 69.162.124.237 – for future use
- 69.162.124.238 – 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.

Written by
Tomas Koprusak

Product Owner |

He has worked for Sygic as a marketer and co-led the implementation and development of a product acquired from a competitor. He has also worked as a freelance developer, helping clients from various areas. Tomas brings a wealth of industry experience to our team. He spent a few years in the blockchain industry, leading projects and marketing teams at multiple blockchain-based companies. He has presented products and managed deals in more than 10 countries around the world, managed the ICO, and built a successful marketing team at Fuergy that continues to thrive. Tomas managed a product team for the biggest job site in Slovakia, covering development and transformation to a new B2B app. Not only is Tomas skilled at web development, but he also has a deep understanding of SaaS businesses, which makes him an invaluable asset in shaping and leading various projects at UptimeRobot. His focus is always on the continual improvement of our service and user experience. In addition to his professional achievements, Tomas is a devoted father. His personal interests include cycling (he traveled around the whole country of Slovakia), playing guitar (he even played in a band), servicing bikes, music, and enjoying good beer.

View author profile

Questions? Contact Support

Feature suggestions? Share

14 Comments

Javier Oct 6, 2015 at 9:29 am

Hey UptimeRobot,

Are you planning to add these ips to https://uptimerobot.com/inc/files/ips/IPv4.txt ?

Umut Muhaddisoglu Oct 7, 2015 at 9:29 am

Sorry for the delay.. They are added.

Kristoffer T Oct 14, 2015 at 9:15 am

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?

Umut Muhaddisoglu Oct 16, 2015 at 9:15 am

Just published an IPv4 and IPv6 combined file at: http://uptimerobot.com/locations :)

Paul Oct 27, 2015 at 2:26 pm

Hi Guys,

Some of our monitors which are being checked from 69.162.124.227 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.

Thank you.

Umut Muhaddisoglu Nov 19, 2015 at 2:26 pm

The requests can be coming from the new IPs. Please let us (support@uptimerobot.com) know if the issue still exists.

Damian Dec 11, 2015 at 8:52 am

Hi,
Your IP block appears to be incorrect (only including .224->.228). To include the full IP range, shouldn't it be: IP Block: 69.162.124.224/38

Umut Muhaddisoglu Dec 22, 2015 at 8:52 am

The info looks correct. Here are more details on displaying IP blocks :https://www.mediawiki.org/wiki/Help:Range_blocks .

Dan Crosby Dec 23, 2022 at 8:52 am

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=69.162.124.224&ctype=ipv4&printit=0&x=67&y=18 to confirm.

Tim Smith Jan 12, 2016 at 4:17 pm

Hi,
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

(69\.162\.124\.2(2[6-9]|3[0-8])|
(54\.(79\.28\.129|94\.142\.218|67\.10\.127|64\.67\.106))|46.137.190.132|122.248.234.23|188.226.183.141|178.62.52.237|104.131.107.63)

Hope it's useful (and correct!)
Tim

Tim Smith Jan 12, 2016 at 4:17 pm

Sorry! Just noticed I didn't escape some of the periods

(69\.162\.124\.2(2[6-9]|3[0-8])| (54\.(79\.28\.129|94\.142\.218|67\.10\.127|64\.67\.106))|46\.137\.190\.132|122\.248\.234\.23|188\.226\.183\.141|178\.62\.52\.237|104\.131\.107\.63)