Probe Server Changes [BR,AR,TX]

The following probe server will be changing IP addresses on 2022-08-10:

Dallas, Texas (TX) – USA is changing from

(66.11.113.250 / 2602:ffc5:105:408::2)
to
(163.123.204.130 / 2604:fbc0:3f:0:25:90ff:fea5:555c)

The Latin America Region will be getting IPv6 support and will be changing these IP addresses:

Federal, Argentina (AR) – AR is changing from

(190.104.217.135)
to
(190.210.176.200 / 2803:29a0:ffff:ffff:cd1::2)

São Paulo, Brazil (BR) – BR is changing from

(54.232.120.40)
to
(54.232.120.40 / 2600:1f1e:c8d:1c11::100)

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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2022-08-10 19:16GMT-7] – IP changes complete.

Probe Server Change [NY]

The following probe server will be changing IP addresses on 2022-06-22

New York City, New York (NY) will change from
66.23.202.26 / 2605:9f80:c000:127::2
to
185.43.108.84 / 2a01:6c60:1003::2e6a

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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2022-06-22 9:32GMT-7] – IP change complete.

Probe Server Change [IL]

The following probe server will be changing IP addresses on 2022-04-27

Chicago, Illinois (IL) will change from
172.93.197.58 / 2602:ffc8:1:14:225:90ff:fee6:8f90
to
209.212.145.34 / 2001:1850:1:3:500::22

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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2022-04-27 10:47GMT-7] – IP change complete.

Probe Server Addition [VA]

The following probe server will be added on 2022/03/10:

Ashburn, Virginia (VA) – USA
(172.82.138.70 / 2607:3f00:1:a::10)

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

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

UPDATE: The new probe was added on 2022/03/10 at 18:50 GMT

Notification Profiles

If you often need to add, remove, or change the same notifications on multiple checks, our new notification profiles will save you a lot of time and effort.

You can specify multiple notifications, contact methods or groups and their delays and schedules, in a notification profile and then assign that profile to checks. When you need to change the notifications, simply change it in the profile without having to edit those checks.

Notification profiles are also available through our API and can simplify the creation of checks.

NodePing uptime notifications are fast and accurate. If you do not have a NodePing account, please sign up for our 15-day, free trial and you’ll be the first to know when your services are offline.

Probe Server Removal [NC]

The following probe server will be removed on 2022-01-20:

Charlotte, North Carolina (NC) – USA
(172.82.138.70 / 2607:3f00:1:a::10)

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2022-01-20 12:41GMT-7] – IP removal complete.

Probe Server Addition [NZ]

The following probe server will be added on 2021/12/08:

Auckland, New Zealand (NZ) – NZ
(163.47.21.47 / 2406:d500:5::9d4e:fd08)

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

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2021-12-08 11:51GMT-7] – IP addition complete.

Free SSL Certificates for Public Status Reports

We’ve added a free ACME SSL provider integration to our Status Reports so your public status pages can be accessed on TLS-secure URLs.

NodePing public status reports provide a visible indicator of your website and service status and you can set those reports to be accessible to any subdomain you control. It’s easy to have your status page show up on http://status.example.com. You need only add the custom domain to your public report and set a DNS record.

Now with free SSL certs from Let’s Encrypt™, just by setting one additional CNAME record in your DNS, you can also have your public status pages show up on TLS-secure URLs like https://status.example.com.

Detailed instructions about adding SSL to your public status report is available in our documentation.

The new SSL certs are available to both ‘Professional’ and ‘Premiere’ accounts.

If you don’t have a NodePing account yet, please sign up for our free, 15-day trial.

™ is a trademark of Internet Security Research Group. All rights reserved.

Mute Notifications

If it’s server migration or vacation time, it might be time to mute some notifications. NodePing has two new features to help you silence alerts.

Getting actionable alerts from your uptime monitoring to the right people and systems at the right time is an important part of service recovery. Sending unactionable notifications should be avoided as much as possible.

The first new feature is muting notifications on checks. If you know a service is going to be down or flapping you can quiet the notifications on specific checks by clicking on “Mute” in the check edit modal. None of the configured notifications will be sent while the check is muted. You can optionally have the notifications automatically re-enabled as well.

The second new feature is similar but applies to contact methods. For example, if an employee is going on vacation you can mute all notifications to a specific contact method by clicking on the “mute” link in the contact edit modal. When they return, simply click on the ‘unmute’ link to re-enable. You can also optionally have it automatically re-enable notifications for that contact method after a specific time has elapsed.

Both these feature are available now in all NodePing plans and are supported in our API, including Python and Elixir libraries.

If you don’t have a NodePing account, please sign up for our free, 15-day trial and find out how NodePing can help you maximize uptime by reducing failure response times.

Automated Diagnostics and Sub-minute Intervals

We’ve added a couple of new features to help you reduce downtime by keeping a closer eye on your services and getting you the information you need to troubleshoot when they fail.

Sub-minute Intervals

You can now set your check interval to 15 or 30 seconds. Shorter check intervals can detect and alert you to problems more quickly. The faster we detect it, the faster you can respond, the faster your service recovers.

Additional fees apply.

  • 30 second intervals – $0.20/check/month – only applies to enabled checks set to 30-second interval.
  • 15 second intervals – $0.40/check/month – only applies to enabled checks set to 15-second interval.

Sub-minute interval costs are calculated on active peak-usage, are post-paid, and will be charged on your next month’s invoice.

When seconds count, use sub-minute check intervals.

Automated Diagnostics

When a service fails, the first thing you want know is why.

When you enable Automated Diagnostics for a check, as soon as we detect it down, we’ll give you as much information about the failure as we have in the email notification.

For all check types, we provide any DNS resolution and full error message.

Each check type will have the most relevant data for that type. For example: HTTP-type checks, we give you the full request and response headers along with the first 250kb of data returned, SMTP checks, we provide the full SMTP conversation (commands and responses).

That info is sent in the ‘down’ email notification and saved to the event data so you can see it in the check status report.

We also trigger appropriate diagnostics based on the failure.

For timeouts and connection issues, we run an MTR from each probe that verified the failure so you can quickly see if it’s packet-loss, routing issues, or a firewall causing your service to fail.

For DNS issues, we run dig queries against all the listed nameservers for the FQDN so you can see if any are responding with expired or wrong data.

These automated diagnostic results are recorded in the event data for the check and optionally emailed to the contacts listed on the check as soon as we get the results.

This means you get fast and accurate info to help you troubleshoot, which means quicker interventions and less downtime.

Pricing and Plan Changes

Introduced with these new features is our new NodePing pricing changes and plans.

  • Personal – $10/month
  • Professional – $25/month
  • Premiere – $80/month

Additional pricing info can be found on our pricing page.

This is the second plan/pricing change in NodePing’s 10-year history. The last change was 9 years ago (2012). Our costs have risen over the years and the new features are pricey for us to offer.

Existing customers are grandfathered into their current plans/pricing but can upgrade at any time to get access to these new features.

If you do not yet have a NodePing account, please sign up for our free 15-day trial and see for yourself how these great new features reduce your downtime.