Probe server change [SG]

The following probe server will be changing IP addresses on 2017/10/18:

Singapore (SG) – SG is changing from (103.25.202.111 / 2400:c980:0:2:48d:a4ff:fe01:1262) to (103.16.16.30 / 2001:df0:24f:214::10)

Please adjust your firewalls appropriately if you whitelist 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 – 2017-10-18 11:45GMT-6] – IP change complete.

Probe Server Change and Addition [FR,MX]

The following probe server will be changing IP addresses on 2017/09/19:

Paris, France (FR) – FR is changing from (37.59.86.248 / 2001:41d0:a:7a50:5:5:9ab9:a412) to (195.154.167.97 / 2001:bc8:2327:110::10)

We’re also adding a new probe to the Latin America region on 2017/09/19:
Mexico City, Mexico (MX) – MX (138.204.171.109)

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-09-18] – the new probe planned for Mexico will not be added as planned.

[UPDATE – 2017-09-19 10:41GMT-6] – IP change complete.

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.

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.

Site update and feature releases Oct 2016

We’ve rolled out some UI and feature updates for NodePing today. We hope you find them helpful. I’ll summarize the changes here. Look here for future posts, which will go into more details for each.

Delayed Notifications:
You can now set a delay on ‘down’ alerts. This will help make your notifications more actionable for frequently flapping services. This new feature can also be used to escalate alerts or notify support/management if services remain offline. This feature has been available for a while in our API, but hasn’t been in our documentation, and has now been added to our UI as well. See the ‘Delay’ drop down in the Notification section of your check.

Check Cloning:
You can now clone an existing check, with all its settings, in our UI to create a new check. This will help reduce “clickty-clickty” syndrome when setting up a lot of checks with similar settings. Click on the label of the check you want to clone to display the details to reveal the ‘Clone Check’ link on the far right.

Notification Dependencies:
When an edge router or server fails, it’s assumed that all the services that depend on them will also fail. It’s not helpful to receive hundreds of alerts for dependent services. You can now set another check as a notification dependency on each check. If the dependent check is already failing, notifications will be suppressed. Use this to avoid alert floods when bottleneck services fail. You can find the ‘Dependency’ drop down in the Notification section of each check.

Disable All Notifications:
There is now a link in the Contacts tab to “Disable notifications”. Use this to suppress all alerts until you re-enable them using the same link. It’s another way to help avoid the distraction of alert floods during big outages.

Disable Checks:
Now you can disable multiple checks with one click. You’ll find the “Disable All Checks” link in the Account Settings – General Settings tab. You can also apply filters based on label, target, or check type to, for example, disable all PING checks or all checks pointing to “example.com”. Use this to disable checks during planned outages/maintenance or to quiet down your logs when troubleshooting.

All the above new features, except check cloning, are also available via our API. If you have any questions about these new features, reach out to support@nodeping.com; we’re happy to help.