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

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.

 

If you find Uptime Robot useful, help us spreading the word:

Comments

    1. Umut Muhaddisoglu Post author

      Sorry for the delay.. They are added.

      Reply
  1. Kristoffer T

    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?

    Reply
  2. Paul

    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.

    Reply
    1. Umut Muhaddisoglu Post author

      The requests can be coming from the new IPs. Please let us ([email protected]) know if the issue still exists.

      Reply
  3. Damian

    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

    Reply
  4. Tim Smith

    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

    Reply
    1. Tim Smith

      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)

      Reply
  5. Andy Whitcroft

    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):

    https://uptimerobot.com/inc/files/ips/IPv4-blocks.txt:
    74.86.158.104/29
    69.162.124.224/28
    46.137.190.132
    [...]

    Thanks.

    -apw

    Reply
    1. Umut Muhaddisoglu Post author

      We’ll definitely be adding the blocks very soon.

      Reply
  6. Patrick

    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?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>