updown.io: IPs & Locations
Verified updown.io IP Addresses. Copy-Paste Firewall-Setups.
Every official updown.io 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.
11 IPv4 and 11 IPv6 addresses across 11 nodes 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.
updown.io 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 updown.io Monitoring IPs
updown.io publishes its monitoring nodes (including IPs) as JSON at updown.io/api/nodes, plus plain lists at /api/nodes.ipv4 and /api/nodes.ipv6.
updown.io is a lightweight, developer-focused uptime monitoring service from France. It checks your site from a small set of named nodes spread across Europe, North America, Asia-Pacific, and Africa — every node and its IP addresses are published via a public API.
With such a compact node list, whitelisting is quick — but it also means a single blocked node skews results immediately. Add all addresses below to your allow list.
This list contains 11 IPv4 and 11 IPv6 addresses, verified against the official source on 2026-06-12.
IPv4 addresses 11
- 45.32.74.41
- 104.238.136.194
- 192.99.37.47
- 91.121.222.175
- 104.238.159.87
- 102.212.60.78
- 135.181.102.135
- 45.32.107.181
- 45.76.104.117
- 45.63.29.207
- 178.63.21.176
IPv6 addresses 11
- 2001:19f0:6001:2c6::1
- 2001:19f0:9002:11a::1
- 2607:5300:60:4c2f::1
- 2001:41d0:2:85af::1
- 2001:19f0:6c01:145::1
- 2c0f:c40:4003:4::2
- 2a01:4f9:c010:d5f9::1
- 2001:19f0:4400:402e::1
- 2001:19f0:7001:45a::1
- 2001:19f0:5801:1d8::1
- 2a01:4f8:141:441a::2
Last verified: 2026-06-12
Official source: https://updown.io/api/nodes
Where updown.io Checks From
Official location data from the provider — addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Cape Town, South Africa | 102.212.60.782c0f:c40:4003:4::2 |
| Falkenstein, Germany | 178.63.21.1762a01:4f8:141:441a::2 |
| Frankfurt, Germany | 104.238.159.872001:19f0:6c01:145::1 |
| Helsinki, Finland | 135.181.102.1352a01:4f9:c010:d5f9::1 |
| Los Angeles, US | 45.32.74.412001:19f0:6001:2c6::1 |
| Miami, US | 104.238.136.1942001:19f0:9002:11a::1 |
| Montreal, Canada | 192.99.37.472607:5300:60:4c2f::1 |
| Roubaix, France | 91.121.222.1752001:41d0:2:85af::1 |
| Singapore, Singapore | 45.32.107.1812001:19f0:4400:402e::1 |
| Sydney, Australia | 45.63.29.2072001:19f0:5801:1d8::1 |
| Tokyo, Japan | 45.76.104.1172001:19f0:7001:45a::1 |
Whitelisting updown.io-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 45.32.74.41 ufw allow from 104.238.136.194 ufw allow from 192.99.37.47 ufw allow from 91.121.222.175 ufw allow from 104.238.159.87 ufw allow from 102.212.60.78 ufw allow from 135.181.102.135 ufw allow from 45.32.107.181 ufw allow from 45.76.104.117 ufw allow from 45.63.29.207 ufw allow from 178.63.21.176 ufw allow from 2001:19f0:6001:2c6::1 ufw allow from 2001:19f0:9002:11a::1 ufw allow from 2607:5300:60:4c2f::1 ufw allow from 2001:41d0:2:85af::1 ufw allow from 2001:19f0:6c01:145::1 ufw allow from 2c0f:c40:4003:4::2 ufw allow from 2a01:4f9:c010:d5f9::1 ufw allow from 2001:19f0:4400:402e::1 ufw allow from 2001:19f0:7001:45a::1 ufw allow from 2001:19f0:5801:1d8::1 ufw allow from 2a01:4f8:141:441a::2
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
The canonical source is the public API: updown.io/api/nodes returns all nodes with IPv4/IPv6 and location metadata; /api/nodes.ipv4 and /api/nodes.ipv6 return plain lists that are easy to consume in firewall automation.
Around a dozen named nodes worldwide (Europe, North America, Asia-Pacific, Africa). You select per check which locations are used.
Yes, every node has both an IPv4 and an IPv6 address. Whitelist both lists for dual-stacked infrastructure.
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 updown.io and are published by updown.io 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 updown.io. 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.