NodePing UI Update

NodePing’s typical users are looking for quick access to a lot of information about their monitoring. Historically, we have leaned into that need for data, and provided an information dense UI. When we updated the UI in 2024, we added some access to technical data, and in other ways dialed back how dense the UI appeared. We’ve been missing some aspects of the way the legacy UI displayed information ever since.

We are now releasing another fairly large update to our UI, which for many customers who have been using NodePing since before 2024 will feel somewhat familiar. One big feature from the original UI that we’re bringing back is the drawers in the check list, which gives you immediate information about your checks without navigating away from the list, and allows you to easily have multiple checks’ details in view. We’ve also worked to streamline some of how you manage contacts and contact methods.

The update also adds some functionality, building on the things that we did like about the 2024 update. One big feature we’ve been asked about many times is MFA (multi factor authentication), which is included in this update. This is in addition to our support for third party OIDC logins. The update provides support one time email links and codes, single use backup codes you can create and retain to access the service, and authenticator app integration (using Google’s Authenticator App, for example). All of this is, of course, optional. If you don’t need MFA you can continue to login as you always have. More MFA features are in the works. Per user MFA is configured in the user’s contact.

There are a handful of other enhancements loaded in there as well. We have worked to streamline some settings management. Maintenance now supports saving maintenance settings as maintenance templates so you can more easily add new ones later. We’ve also improved performance of the UI for large numbers of checks. Most of our customers with thousands of checks manage that through the API, but there are situations in which you may need to find and work with checks in the UI even if you have thousands of them.

We have more in the queue. Your feedback is important to us. In fact, feedback is a big part of the reason this update exists. So please let us know what you think, and what is important to you going forward. So please either email support, or use our Contact form.

And if you don’t yet have a NodePing account, try it! We provide free, no-commitment trials, and there is no downside to trying it out.

Probe Server Change [JP] & [NZ]

We will be changing the IPv6 IPs for the following probe servers in the EAO region on 2026-08-05:

Note: IPv4 addresses for these servers are NOT changing

Tokyo, Japan [JP] – JP changing from:
(2406:d500:15:3::a)
to:
(2406:d500:15:2::3)

Auckland, New Zealand [NZ] – NZ changing from:
(2406:d500:14:13::10)
to:
(2406:d500:14:2::c5)

Please adjust your firewalls appropriately if you whitelist.

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 IPv6 changes were not completed.

Probe Server Removal [PE] & [AR]

The following probe servers will be removed immediately:

EAO Region:
Perth, Australia (PE) – AU
(203.29.240.44 / 2404:9400:4:0:216:3eff:fee1:3c1b)

LAM Region:
Buenos Aires, Argentina (AR) – AR
(190.210.176.200 / 2803:29a0:ffff:ffff:cd1::2)

Please adjust your firewalls appropriately if you whitelist.

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.

Probe Server Change [NZ]

We will be changing the following probe server in the EAO region on 2026-4-28:

Auckland, New Zealand [NZ] – NZ changing from:
(163.47.21.47 / 2406:d500:5::9d4e:fd08)
to:
(163.47.21.230 / 2406:d500:14:13::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, a text file, and via DNS query: probes.nodeping.com.

[UPDATE – 2026-4-28 11:00 GMT-6] – IP change complete.

Probe Server Change [IL]

We will be changing the following probe server in the NAM region on 2026-3-31:

Chicago, Illinois [IL] – USA changing from:
(209.212.145.34 / 2001:1850:1:3:500::22)
to:
(104.36.231.106 / 2607:a680:2:1012::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, a text file, and via DNS query: probes.nodeping.com.

[UPDATE – 2026-3-31 9:45 GMT-6] – IP change complete.

New Africa Region [NG, EG, ZA] & Probe Addition [FL]

We’re excited to announce we’re adding a new check region and probe servers in Africa to the NodePing server monitoring service.

The new region will be brought online and available for selection starting February 11, 2026. With this new addition, NodePing now has five distinct check regions, North America (NAM), Europe (EUR), East Asia/Oceania (EAO), Latin America (LAM), and Africa (AFR).

The new probe servers are located in:

  • Lagos, Nigeria (NG)
    (185.255.123.184)
  • Cairo, Egypt (EG)
    (104.166.138.234)
  • Johannesburg, South Africa (ZA)
    (65.255.42.194)

You can specify our new Africa region as the default region on your account or select it as a region on individual checks to get results from these new probe servers. Be advised that IPv6 is not available on these hosts yet and they won’t be included in the World Wide region, WLW.

Additionally, we will be adding the following probe server in the NAM & LAM region on 2026-2-11:

Miami, Florida (FL) – USA
(192.73.243.238 / 2607:f740:17::4b0)

Please adjust your firewalls appropriately if you whitelist so your checks do not fail because of the probe IP additions.
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 – 2026-01-14 16:30 GMT-7] – Probe additions complete. Africa region is now available, be advised that IPv6 is not available on these hosts yet and they won’t be included in the World Wide region, WLW.

Probe Server Changes [FL & WA]

We will be changing the following probe servers in the NAM region on 2026-1-13:

Miami, Florida (FL) – USA changing from:
(162.254.202.35 / 2604:bc80:8001:3c:225:90ff:fee5:5c6)
to:
(167.253.66.14 / 2602:fcc0:2222:fd8c::10)

Seattle, Washington (WA) – USA changing from:
(107.161.26.107 / 2604:180:1:6e::83b5)
to:
(216.106.186.150 / 2604:86c0:5001:5::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, a text file, and via DNS query: probes.nodeping.com.

[UPDATE – 2026-01-14 11:29 GMT-7] – WA IP change complete. FL IP changed failed and the FL probe has been removed from our system.

Probe Server Change [MI]

We will be changing the following probe server in the NAM region on 2025-11-05:

Detroit, Michigan (MI) – USA changing from:
(74.80.184.138 / 2620:11f:7001:3::10)
to:
(216.106.180.136 / 2604:86c0:b001:5::2)

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

[UPDATE – 2025-11-05 11:36 GMT-6] – IP change complete.

Probe Server Change [AZ]

We will be changing the following probe server in the NAM region on 2025-10-09:

Phoenix, Arizona (AZ) – USA
(136.175.8.15 / 2605:8340:0:1::2)
to
(38.114.123.177 / 2604:86c0:a001:e::2)

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

[UPDATE – 2025-10-09 10:57GMT-7] – IP change complete.

RDAP Monitoring

Announcing: RDAP Check type — A Smarter Way to Watch Your Domains

We’re excited to introduce our newest monitoring check type, RDAP. Ever wish you could proactively know when your domains are about to expire, or ensure the nameservers configured at your registrar haven’t been changed? RDAP Checks make it easy.

What Is an RDAP Check?

RDAP (Registration Data Access Protocol) is essentially a modern, structured successor to WHOIS, letting you pull domain, ASN, or IP registration data over HTTP in JSON format. Unlike legacy WHOIS queries, RDAP delivers rich, programmable data with support for internationalization and extensibility about.rdap.org.

Now, NodePing can monitor that data for you! Use RDAP Checks to:

  • Stay ahead of domain expiration — never forget that renewal.
  • Ensure infrastructure consistency — verify nameservers and registration data on your schedule.
  • Monitor your RDAP services — get alerted instantly if your RDAP endpoint goes down.
  • Get actionable feedback — diagnostics help you pinpoint the issue faster.

At NodePing we strive to make monitoring smarter, easier, and more versatile. RDAP Checks slot right into that vision—whether you’re managing domains, enforcing infrastructure integrity, or keeping your RDAP services reliable.

Ready to try it? Head to your NodePing dashboard and give RDAP Checks a spin. Don’t have an account yet? No problem, sign up for a free, 15-day trial. As always, support is just an email away if you need help making it perfect.