Probe Server Changes and Addition [IT,FR,TX,OR]

The following probe servers will be changing IP addresses on 2017/05/18:

Milan, Italy (IT) – IT is changing from (95.141.35.64 / 2a02:29e0:1:232::2) to (185.93.183.12 / 2001:ac8:24::40)
Paris, France (FR) – FR is changing only ipv6 from (2001:41d0:d:12ac:1:1:1212:70c1) to (2001:41d0:a:7a50:5:5:9ab9:a412)
Dallas, Texas (TX) – US is changing from (104.200.142.50 / 2607:f7a0:2:0:ec4:7aff:fe15:dcce) to (45.58.61.34 / 2604:6600:2000:c::2)

We’re also adding a new server to the North America region on 2017/05/18:
Portland, Oregon (OR) – US (69.163.39.244 / 2605:ea00:1:1:d267:e5ff:fee7:51c)

We’re also removing one probe from our Latin America region:
Panama (PA) – PA (190.14.37.189)

Please adjust your firewalls appropriately if you whitelist so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2017-05-18 11:30GMT-4] – IP changes and probe addition complete.

Probe Server Changes – [PY,IT]

The following probe servers will be changing IP addresses on 2017/04/04:

Philadelphia, Pennsylvania (PY) – USA is changing from (162.208.50.172 / 2607:2200:0:3701:0:8:0:10) to (154.16.159.242 / 2604:bf00:210:1d::2)
Milan, Italy (IT) – IT is changing from (194.14.179.117 / 2a00:dcc0:eda:89:14:179:4f75:4e2) to (95.141.35.64 / 2a02:29e0:1:232::2)

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2017-04-04 10:57GMT-4] – IP changes complete.

Probe Server Changes – [CA,GA,IL,TX]

The following probe servers will be changing IP addresses on 2017/03/01:

Los Angeles, California (CA) – USA is changing from 162.211.65.254 to 184.170.243.202.
Atlanta, Georgia (GA) – USA is changing from 192.30.32.170 to 66.71.251.162.
Chicago, Illinois (IL) – USA is changing from 162.211.66.130 to  104.128.57.130.
Dallas, Texas (TX) – USA is changing from 107.155.66.30 to 104.200.142.50.

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2017-03-01 10:50GMT-5] – IP changes complete.

Diagnostic Tools

“Why is my check failing?”

It isn’t always obvious what’s causing the failure when a check does ‘down’ and additional information about what our probes are experiencing can be helpful. For example, if your website is timing out, is it the web server, a DNS problem, or maybe packet loss on the network?

Our new diagnostic tools allow you to run several utilities on our probes and give visibility to what our probes are seeing to help you troubleshoot a failing service. These tools can be useful to narrow down where the failure is so you can get things fixed and services restored as quickly as possible.

Tools available:

  • Ping
  • Traceroute
  • MTR
  • Dig
  • Page Load (browser loading with page speed – HAR viewer)
  • Screenshot

More information about the tools and some troubleshooting advice can be found in our documentation.

You can find these tools on the “Diagnostic Tools” tab when you login to your NodePing account.  If you don’t yet have a NodePing account, you can create one and try out these tools with our 15-day, free uptime monitoring trial.

What other tools would be helpful on that page? Let us know in the comments.

Probe Server Changes – [NC,UK]

The following probe servers will be changing IP addresses on 2017/01/18:

North Carolina (NC) is changing from 104.225.1.179 in Cary to 64.187.224.66 in Asheville
England (UK)  will change from 146.185.21.51 in London to 194.187.248.8 in Manchester

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2017-01-17 11:18GMT-5] – IP changes complete.

Probe Server IP Address Change – [PY]

Our probe in Philadelphia, Pennsylvania, USA, will be changing IP addresses on 2016/12/07:
Philadelphia, Pennsylvania (PY) is changing from 162.208.48.232 to 162.208.50.172.

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address change.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2016-12-07 17:39GMT-5] – IP change complete.

Notification Dependencies

Oh no! A power supply failure has taken your website server offline and here comes 120 HTTP ‘down’ notifications from NodePing. When a major outage hits, the last thing you need is an alert flood for all the checks you already know are bound to fail.

When a check depends on other services or networks, you don’t need more notifications that it’s failing when you already know the service that it depends on is failing. NodePing recently released a new feature called ‘Notification Dependency’ to help mitigate that unhelpful alert flood.

Set a ‘Notification Dependency’ on your checks when you want to suppress notifications for checks that depend on another check for availability. Web sites on the same web server can all be set to have their HTTP checks dependent on the server PING check. Or, you can set server PING checks to be dependent on the network router PORT check. If the dependent check is failing, no notifications will be sent for the check. The checks will still fail, only alerts won’t be sent for those failures.

Choose your dependent check from the ‘Dependency’ dropdown in the ‘Notifications’ section of the check edit modal and then ‘Save’ your changes for that check.

Notification dependencies are another way to help you receive only actionable alerts for your uptime monitoring and are available to all NodePing customers.

If you aren’t using NodePing server monitoring yet, sign up for your free, 15-day trial today.