Redis Monitoring

Redis is a very popular key/value store used by many web applications for sessions, caching, or as a main datastore. Its lightning fast, in-memory model has three versatile modes: standalone, sentinel, and cluster.

  • Redis standalone instance runs on a single host and provides quick access to data.
  • Redis sentinel mode will provide automated failover to a secondary host should the primary be unavailable to the sentinels.
  • Redis cluster instance shards your data so even the largest datasets can be accessed with the near instantaneous response Redis is famous for.

NodePing’s Redis check can monitor availability of all three instance types. You’ll be the first to know if your Redis hosts or sentinels are offline.

The check connects to your Redis instance, runs an INFO command, and waits for a valid response. If our probe can’t connect, gets an authentication error, or receives no response, we’ll verify the outage and send notifications. The faster you know, the faster the fix, the more uptime.

Redis is often used as a mission-critical datastore. Don’t let a Redis outage go unnoticed. Use NodePing’s Redis monitoring.

If you don’t have a NodePing account yet, sign up for our free, 15-day trial and see for yourself why those who know use NodePing.

Private Key Authentication for SSH Monitoring

Now you can monitor your SSH services using private key authentication with NodePing’s SSH check.

NodePing has supported password authentication for SSH monitoring for many years but starting today we’ve added support for key-based authentication. You’ll be the first to know when SSH services are offline. Faster detection means faster intervention which means less downtime.

Our SSH check can not only verify that your SSH services are up and running but also match a string in the console output. It’s a great feature if you, for example, want to make sure your database is up and running but don’t want to punch another hole in your firewall. Have your login script run a CLI database query and pipe the output to stdout before closing the SSH connection. If the host is offline, or SSH isn’t working, or your database isn’t responding correctly, the check will fail and you’ll get quick notifications.

We have an important ‘SSH monitoring best practices‘ post over on the NodePing site to help you mitigate the risks associated with SSH monitoring. In particular, consideration should be given to the Security Considerations section.

We’ve also updated our Terms of Service to reflect this new functionality and its risks.

SSH private key authentication is available on the ‘Premiere‘ plan. If you don’t have a NodePing account yet, sign up for our free, 15-day trial and see for yourself how with NodePing you will be the first to know when important services are down.

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.