NodePing: IPs & Locations
Verified NodePing IP Addresses. Copy-Paste Firewall-Setups.
Every official NodePing monitoring IP: verified in real-time against the canonical source, featuring ready-to-use firewall templates. Stop false downtime alerts caused by blocked checking nodes on your infrastructure.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
Three-Step Activation & Frictionless Firewall Alignment
Bring your perimeter security rules up to date in three simple steps. Our production-ready configuration templates for common server architectures eliminate fragmented routing filters and costly check flapping.
30 IPv4 and 27 IPv6 addresses from 30 probe locations worldwide: one click below copies everything as a plain list or as ready-to-paste UFW, nginx, or Apache config.
Add every address to your allow list: UFW, nginx, Apache, or a Cloudflare/WAF skip rule. Partial lists cause flapping checks and false alerts.
NodePing updates its list occasionally. This page was verified on 2026-06-12 against the official source. Re-check after unexplained alerts or automate the sync.
Official NodePing Monitoring IPs
NodePing lists every probe with location, IPv4, and IPv6 in its official FAQ.
NodePing is a no-frills uptime monitoring service with one-minute checks from probes around the world. When a check fails at one probe, NodePing automatically rechecks from other regions before alerting, which means partial firewall blocks produce confusing, flapping results.
Whitelist every probe below. NodePing documents each probe with its location, IPv4, and IPv6 address in the official FAQ.
This list contains 30 IPv4 and 27 IPv6 addresses, verified against the official source on 2026-06-12.
IPv4 addresses 30
- 38.114.123.177
- 104.247.192.170
- 216.106.186.150
- 173.248.161.42
- 38.114.122.106
- 104.36.231.106
- 216.106.180.136
- 64.79.76.50
- 169.197.141.113
- 199.233.235.34
- 23.111.153.22
- 192.73.243.238
- 5.226.139.158
- 163.172.52.132
- 37.252.125.64
- 54.36.110.96
- 217.182.201.227
- 95.216.64.250
- 23.166.88.115
- 45.77.48.69
- 144.48.37.241
- 172.104.181.238
- 103.6.85.58
- 180.149.230.17
- 163.47.21.230
- 148.163.220.117
- 64.176.5.76
- 185.255.123.184
- 104.166.138.234
- 65.255.42.194
IPv6 addresses 27
- 2604:86c0:a001:e::2
- 2607:3f00:11:21::10
- 2604:86c0:5001:5::10
- 2607:fc88:100:40::2
- 2604:86c0:4001:2::2
- 2607:a680:2:1012::10
- 2604:86c0:b001:5::2
- 2001:1828:0:f6::2
- 2604:86c0:3001:10::2
- 2607:3f00:1:a::10
- 2604:4500:5:54::10
- 2607:f740:17::4b0
- 2a01:4020:1:26::10
- 2001:bc8:2327:101::10
- 2a02:2770:5:0:21a:4aff:fe1a:c131
- 2001:41d0:700:1360::10
- 2001:41d0:602:4e3::10
- 2a01:4f9:2b:105::2
- 2604:86c0:f401:3::2
- 2401:c080:1800:1513:5400:5ff:fe62:f221
- 2406:d500:7:2::43
- 2400:8901::f03c:91ff:feb9:fbf4
- 2403:2500:8000:1::ce6
- 2406:d500:9::7a91:9b75
- 2406:d500:14:13::10
- 2607:f740:1::c85
- 2001:19f0:c800:26bf:5400:05ff:fe3c:dd0f
Last verified: 2026-06-12
Official source: https://nodeping.com/faq.html
Where NodePing Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Phoenix, Arizona (AZ) | 38.114.123.1772604:86c0:a001:e::2 |
| Los Angeles, California (CA) | 104.247.192.1702607:3f00:11:21::10 |
| Seattle, Washington (WA) | 216.106.186.1502604:86c0:5001:5::10 |
| Denver, Colorado (CO) | 173.248.161.422607:fc88:100:40::2 |
| Dallas, Texas (TX) | 38.114.122.1062604:86c0:4001:2::2 |
| Chicago, Illinois (IL) | 104.36.231.1062607:a680:2:1012::10 |
| Detroit, Michigan (MI) | 216.106.180.1362604:86c0:b001:5::2 |
| Columbus, Ohio (OH) | 64.79.76.502001:1828:0:f6::2 |
| New York City, New York (NY) | 169.197.141.1132604:86c0:3001:10::2 |
| Ashburn, Virginia (VA) | 199.233.235.342607:3f00:1:a::10 |
| Atlanta, Georgia (GA) | 23.111.153.222604:4500:5:54::10 |
| Miami, Florida (FL) | 192.73.243.2382607:f740:17::4b0 |
| London, England (LD) | 5.226.139.1582a01:4020:1:26::10 |
| Paris, France (FR) | 163.172.52.1322001:bc8:2327:101::10 |
| Amsterdam, Netherlands (NL) | 37.252.125.642a02:2770:5:0:21a:4aff:fe1a:c131 |
| Frankfurt, Germany (DE) | 54.36.110.962001:41d0:700:1360::10 |
| Warsaw, Poland (PL) | 217.182.201.2272001:41d0:602:4e3::10 |
| Helsinki, Finland (FI) | 95.216.64.2502a01:4f9:2b:105::2 |
| Zurich, Switzerland (CH) | 23.166.88.1152604:86c0:f401:3::2 |
| Sydney, Australia (AU) | 45.77.48.692401:c080:1800:1513:5400:5ff:fe62:f221 |
| Melbourne, Australia (AM) | 144.48.37.2412406:d500:7:2::43 |
| Singapore (SG) | 172.104.181.2382400:8901::f03c:91ff:feb9:fbf4 |
| Hong Kong (HK) | 103.6.85.582403:2500:8000:1::ce6 |
| Tokyo, Japan (JP) | 180.149.230.172406:d500:9::7a91:9b75 |
| Auckland, New Zealand (NZ) | 163.47.21.2302406:d500:14:13::10 |
| Sao Paulo, Brazil (BR) | 148.163.220.1172607:f740:1::c85 |
| Santiago, Chile (CL) | 64.176.5.762001:19f0:c800:26bf:5400:05ff:fe3c:dd0f |
| Lagos, Nigeria (NG) | 185.255.123.184 |
| Cairo, Egypt (EG) | 104.166.138.234 |
| Johannesburg, South Africa (ZA) | 65.255.42.194 |
Whitelisting NodePing-Monitoring IPs
Pick a format. The block below contains the complete config for every address in the list above. The plain list is also available as a .txt download.
ufw allow from 38.114.123.177 ufw allow from 104.247.192.170 ufw allow from 216.106.186.150 ufw allow from 173.248.161.42 ufw allow from 38.114.122.106 ufw allow from 104.36.231.106 ufw allow from 216.106.180.136 ufw allow from 64.79.76.50 ufw allow from 169.197.141.113 ufw allow from 199.233.235.34 ufw allow from 23.111.153.22 ufw allow from 192.73.243.238 ufw allow from 5.226.139.158 ufw allow from 163.172.52.132 ufw allow from 37.252.125.64 ufw allow from 54.36.110.96 ufw allow from 217.182.201.227 ufw allow from 95.216.64.250 ufw allow from 23.166.88.115 ufw allow from 45.77.48.69 ufw allow from 144.48.37.241 ufw allow from 172.104.181.238 ufw allow from 103.6.85.58 ufw allow from 180.149.230.17 ufw allow from 163.47.21.230 ufw allow from 148.163.220.117 ufw allow from 64.176.5.76 ufw allow from 185.255.123.184 ufw allow from 104.166.138.234 ufw allow from 65.255.42.194 ufw allow from 2604:86c0:a001:e::2 ufw allow from 2607:3f00:11:21::10 ufw allow from 2604:86c0:5001:5::10 ufw allow from 2607:fc88:100:40::2 ufw allow from 2604:86c0:4001:2::2 ufw allow from 2607:a680:2:1012::10 ufw allow from 2604:86c0:b001:5::2 ufw allow from 2001:1828:0:f6::2 ufw allow from 2604:86c0:3001:10::2 ufw allow from 2607:3f00:1:a::10 ufw allow from 2604:4500:5:54::10 ufw allow from 2607:f740:17::4b0 ufw allow from 2a01:4020:1:26::10 ufw allow from 2001:bc8:2327:101::10 ufw allow from 2a02:2770:5:0:21a:4aff:fe1a:c131 ufw allow from 2001:41d0:700:1360::10 ufw allow from 2001:41d0:602:4e3::10 ufw allow from 2a01:4f9:2b:105::2 ufw allow from 2604:86c0:f401:3::2 ufw allow from 2401:c080:1800:1513:5400:5ff:fe62:f221 ufw allow from 2406:d500:7:2::43 ufw allow from 2400:8901::f03c:91ff:feb9:fbf4 ufw allow from 2403:2500:8000:1::ce6 ufw allow from 2406:d500:9::7a91:9b75 ufw allow from 2406:d500:14:13::10 ufw allow from 2607:f740:1::c85 ufw allow from 2001:19f0:c800:26bf:5400:05ff:fe3c:dd0f
Cloudflare / WAF: create an IP Access Rule (or custom WAF skip rule) with action Allow for the addresses above, so bot fight mode and managed challenges never block probe traffic.
Whitelisting only exempts these addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly.
Frequently Asked Questions
NodePing confirms failures by rechecking from other regions. If some probes are blocked, the confirmation logic sees mixed results and your checks flap between up and down.
Yes. Nearly every probe has a published IPv6 address alongside IPv4. Whitelist both lists for dual-stacked servers.
Occasionally. Probes are added or re-homed. The FAQ is the canonical, always-current source; re-sync it periodically.
Both: wherever requests can be blocked. If your site sits behind a CDN or WAF (Cloudflare, AWS WAF, Akamai…), add an allow/skip rule there so probes are never challenged; if your origin firewall also filters traffic, whitelist them there too. A single missed layer is enough to cause false alerts.
Most providers expose a machine-readable source (linked above). Fetch it on a schedule, a small cron job that pulls the list and updates your firewall ruleset, instead of hardcoding addresses by hand. This page is re-verified against the official source regularly, but automation on your side is the most reliable option.
No. Allow-listing only exempts known monitoring addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly, and authentication, authorization, and TLS are unchanged. You are simply telling your firewall "these are not attackers".
A blocklist keeps known-bad addresses out; an allow/whitelist makes sure known-good addresses, here, the monitoring probes, never end up caught in a block or rate-limit rule. The two coexist: you keep blocking attackers while explicitly exempting the probes.
The IP addresses on this page belong to NodePing and are published by NodePing for whitelisting purposes. List verified on 2026-06-12 against the official source. Always cross-check with the official documentation before locking down production firewalls. All product names and trademarks are the property of their respective owners; Uptimeify is not affiliated with NodePing. Uptimeify's own worker IPs are published at /ips.txt; a feature comparison is on our comparison page.
Monitoring Without IP Guesswork.
Protect your clients' digital assets and lock down your webserver routing. Leverage our verified network catalogs for clean whitelist setups, or migrate directly to the rock-solid, EU-only architecture of Uptimeify.