Creating Clones

Have you ever wanted to be an evil genius and create a clone army to take over the universe? Well, we can’t help you with that but we do have a “Clone Check” feature. It might not take over the universe, but it can be a great time-saver.

ca

When you want to create a check that is similar to one you already have, you can use our “Clone Check” feature to create a new check based on the settings of an existing check. You can then change whichever fields you choose, such as the URL or check type, as well as the label. This saves you from having to type in the various fields over and over or set complicated notifications, delays, etc, when you already have a similar check ripe for cloning.

To clone a check, log into your NodePing account, and go to the “Checks” tab. Click on the label for the check you want to duplicate to open the information drawer. On the lower right, there are a list of links, including “Clone Check”. Clicking on it will bring up a new dialog for the cloned check with all of the values preset based on the check you are cloning. You can change the fields to fit the new check you want. Then click “Save” at the bottom of the dialog.

Who knows? If you create enough, maybe you can take over the universe.

Probe Server Changes [AZ,CO]

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

Phoenix, Arizona (AZ) – AZ is changing from (162.253.177.250 / 2602:fff6:5:fba3::baa6) to (104.245.105.2 / 2602:ff97:0:2:225:90ff:fee5:b89)
Denver, Colorado (CO) – CO is changing from (162.211.64.212 / 2602:fff6:d:e301::10fe) to (173.248.161.42 / 2607:fc88:100:40::2)

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-07-06 10:30GMT-6] – IP changes complete.

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.