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.

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.

Probe Server Change [TX] and Addition [NC]

The following probe server will be changing IP addresses on 2021-06-16:

Dallas, Texas (TX) – USA is changing from

(45.56.73.70 / 2600:3c00::f03c:92ff:feaa:d919)
to
(66.11.113.250 / 2602:ffc5:105:408::2)

We are also adding a new probe to the North America region on 2021-06-16:

Charlotte, North Carolina (NC) – 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 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 – 2021-06-16 12:40] – IP change and addition complete. The 2-letter probe indicator for the new probe was incorrectly announced last week. The proper probe indicator is “nc” instead of “va”.

Probe Server Change [CA]

The following probe server will be changing IP addresses on 2021-03-18

Los Angeles, California (CA) will change from
192.161.172.202 / 2607:fcd0:106:ab01::10
to
104.247.192.170 / 2607:3f00:11:21::10

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 – 2021-03-18 11:57GMT-7] – IP change complete.

Probe Server Change [AU] and Addition [FI]

The following probe server will be changing IP addresses on 2021-02-24

Sydney, Australia (AU) – AU is changing from
139.99.130.48 / 2402:1f00:8100:230::10
to
112.213.38.162 / 2404:9400:2:0:216:3eff:fee1:bce0

We are also adding a new probe to the Europe region on 2021-02-24

Helsinki, Finland (FI) – FI
95.216.64.250 / 2a01:4f9:2b:105::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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2021-02-24 12:29GMT-7] – IP change and probe addition complete.

DoH Monitoring and DoT Monitoring

NodePing can verify that your DNS over HTTPS (DoH) and DNS over TLS (DoT) services are available and replying with the expected records.

DoH/DoT was created to help secure DNS queries and responses over untrusted networks and is supported by most browsers and operating systems.

Our DoH/DoT check will ensure that your DNS over HTTPS (RFC 8484) or DNS over TLS (RFC 7858) servers are working correctly and if they’re not, we’ll send you notifications.

In accordance with the RFCs, our uptime monitoring for DoH uses the common DNS wire format via HTTPS GET or POST over port 443. Our uptime monitoring for DoT also uses DNS wire format over via TLS over port 853. You can include EDNS(0) OPT records in the queries as well as verify the query response. You can add custom HTTP headers (DoH-only) and sign your requests with your own TLS client certificates for authentication.

The DoH/DoT check can be found in the standard check type drop down menu in your NodePing account. If you don’t have a NodePing account yet, please sign up for our 15-day, free trial.

Probe Changes [NJ, TX, WA] and Removal [GA, RO]

The following probe servers will be removed on 2021-01-14:

Atlanta, Georgia (GA) – USA (107.150.22.26 / 2607:fcd0:aa80:2200::10)
Bucharest, Romania (RO) – RO (185.158.248.112 / 2a04:9dc0:0:4:185:158:248:112)

The following probe servers will be changing IP addresses on 2021-01-14

Seattle, Washington (WA) – USA (173.205.92.154 / 2607:fcd0:cd00:a00::10)
will change to
(107.161.26.107 / 2604:180:1:6e::83b5)

Dallas, Texas (TX) – USA (198.96.95.50 / 2607:fcd0:da80:4300::10)
will change to
(45.56.73.70 / 2600:3c00::f03c:92ff:feaa:d919)

Newark, New Jersey (NJ) – USA (23.226.135.34 /2607:fcd0:ccc0:1301::10)
will change to
(209.205.207.243 / 2a06:8640:198::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, a text file, and via DNS query, probes.nodeping.com.

[UPDATE – 2021-01-14 13:00GMT-7] – IP changes and probe removals complete.

Compact View for Status Reports

When we released our new status reporting recently one of the first requests was for a compact view of checks on the report.  People wanted a view that would put a list of checks statuses on the screen all at once.  So we’re happy to be releasing a more compact view of the list of checks on the report.

The new “compact” view can be turned on in the “Checks” section of the report configuration  The layout uses a table, so some of the features of the standard view (like setting the sort order) aren’t relevant to the table based view.  However, you can still pick what uptime metrics to show.  If you pick an uptime display that has more than four or five columns, you will likely want to adjust the display width of the report.  How to do that is discussed on our Report Styling page in the documentation.  

Our old status reporting showed seven days and thirty days of uptime, which wasn’t included in the first release of the new report.  In addition to the compact view, we’re also adding the seven+thirty uptime view.  It’s also available in the Checks section of the status report configuration, as well as in the Uptime section of the configuration for individual check status pages.

Both of these enhancements to the report were in direct response to feedback we got from customers on the new reporting.  There are more enhancements coming as well.  We listen to feedback, and base many of our decisions on future enhancements on what our customers are requesting.  So please let us know what is important to how you use our monitoring tools.

And if you don’t use NodePing yet, the best thing to do is get started with a free, 15-day trial.