Oh Dear: IPs & Locations
Verified Oh Dear IP Addresses. Copy-Paste Firewall-Setups.
Every official Oh Dear 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.
43 IPv4 and 31 IPv6 addresses from 17 published check locations: 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.
Oh Dear 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 Oh Dear Monitoring IPs
Oh Dear publishes its full server list (IPv4/IPv6 + locations) at ohdear.app/used-ips.json.
Oh Dear is a Belgian all-in-one monitoring service, uptime, certificate health, broken links, scheduled tasks, well known in the Laravel and PHP community. All checks run from a published fleet of servers spread across the globe, each with IPv4 and IPv6 addresses.
Whitelist the complete list below so firewall or bot-protection rules never turn a healthy site into a false "down" alert.
This list contains 43 IPv4 and 31 IPv6 addresses, verified against the official source on 2026-06-12.
IPv4 addresses 43
- 45.32.146.84
- 139.59.61.47
- 45.76.59.200
- 45.32.189.194
- 45.76.46.251
- 165.22.95.234
- 95.179.211.184
- 167.71.54.244
- 45.76.236.54
- 167.172.97.55
- 164.90.176.102
- 199.247.9.185
- 217.69.10.40
- 159.203.38.39
- 198.13.48.175
- 46.101.122.201
- 158.247.212.166
- 45.32.107.252
- 165.227.31.113
- 45.63.54.118
- 178.62.45.205
- 134.209.122.208
- 13.245.37.23
- 54.94.4.151
- 45.32.147.8
- 134.209.243.63
- 138.68.138.12
- 138.68.138.180
- 104.236.192.248
- 165.22.36.80
- 159.203.60.48
- 216.128.128.104
- 70.34.203.58
- 217.19.225.103
- 176.62.160.106
- 23.88.67.24
- 167.71.40.86
- 167.71.57.77
- 137.184.22.216
- 159.65.3.76
- 142.93.110.196
- 68.183.121.207
- 167.99.69.81
IPv6 addresses 31
- 2001:19f0:6801:5f3:5400:1ff:fe38:3572
- 2400:6180:100:d0::12:e001
- 2001:19f0:6401:f5a:5400:1ff:fe57:57e9
- 2001:19f0:5801:1e90:5400:1ff:fecb:f1f2
- 2001:19f0:6801:15d7:5400:1ff:fef9:8e1d
- 2a03:b0c0:3:e0::220:2001
- 2a05:f480:1c00:7dd:5400:2ff:fe68:af7
- 2a03:b0c0:3:e0::2a8:6001
- 2001:19f0:6401:19d5:5400:2ff:feb3:6d28
- 2a03:b0c0:3:e0::386:1
- 2a03:b0c0:3:f0::173:0
- 2a05:f480:1c00:c80:5400:2ff:feda:ca89
- 2001:19f0:6801:9d3:5400:2ff:feda:fb6e
- 2604:a880:cad:d0::7aa:6001
- 2001:19f0:7002:3d5:5400:2ff:fedb:8dc0
- 2a03:b0c0:3:d0::10b8:8001
- 2401:c080:1c02:b4:5400:3ff:fe1a:56a2
- 2001:19f0:4400:737b:5400:3ff:fe1a:5634
- 2604:a880:2:d0::15d9:c001
- 2001:19f0:6001:5ef0:5400:3ff:fe1a:5666
- 2a03:b0c0:1:d0::81:e001
- 2604:a880:400:d0::1a7d:4001
- 2a05:f480:1c00:5f0:5400:3ff:fe50:e0c5
- 2a03:b0c0:3:d0::4f5:f001
- 2001:19f0:6401:3a:5400:5ff:fe8b:5e4b
- 2a05:f480:2000:295b:5400:5ff:fe85:e8c9
- 2a01:4f8:272:426a::2
- 2a03:b0c0:3:d0::e8d:1001
- 2a03:b0c0:3:f0:0:1:8224:4000
- 2604:a880:400:d0::1ce6:d001
- 2400:6180:0:d0::157d:f001
Last verified: 2026-06-12
Official source: https://ohdear.app/docs/general/list-of-ip-addresses-used-by-ohdear
Where Oh Dear Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Bangalore, India | 139.59.61.472400:6180:100:d0::12:e001 |
| Brussels, Belgium | 217.19.225.103 · 176.62.160.106 |
| Cape Town, Africa | 13.245.37.23 |
| Dallas, USA | 45.76.59.200 · 45.76.236.54 · 216.128.128.1042001:19f0:6401:f5a:5400:1ff:fe57:57e9 · 2001:19f0:6401:19d5:5400:2ff:feb3:6d28 · 2001:19f0:6401:3a:5400:5ff:fe8b:5e4b |
| Frankfurt, Germany | 165.22.95.234 · 167.71.54.244 · 167.172.97.55 · 164.90.176.102 · 46.101.122.201 · 134.209.243.63 · 23.88.67.24 · 167.71.40.86 · 167.71.57.77 · 142.93.110.1962a03:b0c0:3:e0::220:2001 · 2a03:b0c0:3:e0::2a8:6001 · 2a03:b0c0:3:e0::386:1 · 2a03:b0c0:3:f0::173:0 · 2a03:b0c0:3:d0::10b8:8001 · 2a03:b0c0:3:d0::4f5:f001 · 2a01:4f8:272:426a::2 · 2a03:b0c0:3:d0::e8d:1001 · 2a03:b0c0:3:f0:0:1:8224:4000 |
| London, UK | 178.62.45.205 · 138.68.138.12 · 138.68.138.1802a03:b0c0:1:d0::81:e001 |
| Los Angeles, USA | 45.63.54.1182001:19f0:6001:5ef0:5400:3ff:fe1a:5666 |
| New York, USA | 134.209.122.208 · 104.236.192.248 · 165.22.36.80 · 137.184.22.216 · 68.183.121.2072604:a880:400:d0::1a7d:4001 · 2604:a880:400:d0::1ce6:d001 |
| Paris, France | 45.32.146.84 · 45.76.46.251 · 95.179.211.184 · 199.247.9.185 · 217.69.10.40 · 45.32.147.82001:19f0:6801:5f3:5400:1ff:fe38:3572 · 2001:19f0:6801:15d7:5400:1ff:fef9:8e1d · 2a05:f480:1c00:7dd:5400:2ff:fe68:af7 · 2a05:f480:1c00:c80:5400:2ff:feda:ca89 · 2001:19f0:6801:9d3:5400:2ff:feda:fb6e · 2a05:f480:1c00:5f0:5400:3ff:fe50:e0c5 |
| San Francisco, USA | 165.227.31.1132604:a880:2:d0::15d9:c001 |
| Sao Paulo, Brazil | 54.94.4.151 |
| Seoul, South-Korea | 158.247.212.1662401:c080:1c02:b4:5400:3ff:fe1a:56a2 |
| Singapore, Singapore | 45.32.107.252 · 159.65.3.76 · 167.99.69.812001:19f0:4400:737b:5400:3ff:fe1a:5634 · 2400:6180:0:d0::157d:f001 |
| Stockholm, Sweden | 70.34.203.582a05:f480:2000:295b:5400:5ff:fe85:e8c9 |
| Sydney, Australia | 45.32.189.1942001:19f0:5801:1e90:5400:1ff:fecb:f1f2 |
| Tokyo, Japan | 198.13.48.1752001:19f0:7002:3d5:5400:2ff:fedb:8dc0 |
| Toronto, Canada | 159.203.38.39 · 159.203.60.482604:a880:cad:d0::7aa:6001 |
Whitelisting Oh Dear-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.146.84 ufw allow from 139.59.61.47 ufw allow from 45.76.59.200 ufw allow from 45.32.189.194 ufw allow from 45.76.46.251 ufw allow from 165.22.95.234 ufw allow from 95.179.211.184 ufw allow from 167.71.54.244 ufw allow from 45.76.236.54 ufw allow from 167.172.97.55 ufw allow from 164.90.176.102 ufw allow from 199.247.9.185 ufw allow from 217.69.10.40 ufw allow from 159.203.38.39 ufw allow from 198.13.48.175 ufw allow from 46.101.122.201 ufw allow from 158.247.212.166 ufw allow from 45.32.107.252 ufw allow from 165.227.31.113 ufw allow from 45.63.54.118 ufw allow from 178.62.45.205 ufw allow from 134.209.122.208 ufw allow from 13.245.37.23 ufw allow from 54.94.4.151 ufw allow from 45.32.147.8 ufw allow from 134.209.243.63 ufw allow from 138.68.138.12 ufw allow from 138.68.138.180 ufw allow from 104.236.192.248 ufw allow from 165.22.36.80 ufw allow from 159.203.60.48 ufw allow from 216.128.128.104 ufw allow from 70.34.203.58 ufw allow from 217.19.225.103 ufw allow from 176.62.160.106 ufw allow from 23.88.67.24 ufw allow from 167.71.40.86 ufw allow from 167.71.57.77 ufw allow from 137.184.22.216 ufw allow from 159.65.3.76 ufw allow from 142.93.110.196 ufw allow from 68.183.121.207 ufw allow from 167.99.69.81 ufw allow from 2001:19f0:6801:5f3:5400:1ff:fe38:3572 ufw allow from 2400:6180:100:d0::12:e001 ufw allow from 2001:19f0:6401:f5a:5400:1ff:fe57:57e9 ufw allow from 2001:19f0:5801:1e90:5400:1ff:fecb:f1f2 ufw allow from 2001:19f0:6801:15d7:5400:1ff:fef9:8e1d ufw allow from 2a03:b0c0:3:e0::220:2001 ufw allow from 2a05:f480:1c00:7dd:5400:2ff:fe68:af7 ufw allow from 2a03:b0c0:3:e0::2a8:6001 ufw allow from 2001:19f0:6401:19d5:5400:2ff:feb3:6d28 ufw allow from 2a03:b0c0:3:e0::386:1 ufw allow from 2a03:b0c0:3:f0::173:0 ufw allow from 2a05:f480:1c00:c80:5400:2ff:feda:ca89 ufw allow from 2001:19f0:6801:9d3:5400:2ff:feda:fb6e ufw allow from 2604:a880:cad:d0::7aa:6001 ufw allow from 2001:19f0:7002:3d5:5400:2ff:fedb:8dc0 ufw allow from 2a03:b0c0:3:d0::10b8:8001 ufw allow from 2401:c080:1c02:b4:5400:3ff:fe1a:56a2 ufw allow from 2001:19f0:4400:737b:5400:3ff:fe1a:5634 ufw allow from 2604:a880:2:d0::15d9:c001 ufw allow from 2001:19f0:6001:5ef0:5400:3ff:fe1a:5666 ufw allow from 2a03:b0c0:1:d0::81:e001 ufw allow from 2604:a880:400:d0::1a7d:4001 ufw allow from 2a05:f480:1c00:5f0:5400:3ff:fe50:e0c5 ufw allow from 2a03:b0c0:3:d0::4f5:f001 ufw allow from 2001:19f0:6401:3a:5400:5ff:fe8b:5e4b ufw allow from 2a05:f480:2000:295b:5400:5ff:fe85:e8c9 ufw allow from 2a01:4f8:272:426a::2 ufw allow from 2a03:b0c0:3:d0::e8d:1001 ufw allow from 2a03:b0c0:3:f0:0:1:8224:4000 ufw allow from 2604:a880:400:d0::1ce6:d001 ufw allow from 2400:6180:0:d0::157d:f001
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 documentation lists all servers, and ohdear.app/used-ips.json provides the same data machine-readable (IPv4, IPv6, and location per server) for firewall automation.
Yes. Every Oh Dear server has both IPv4 and IPv6 addresses. Whitelist both lists if your site is reachable over IPv6.
Occasionally, when servers are added or rotated. Their JSON endpoint 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 Oh Dear and are published by Oh Dear 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 Oh Dear. 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.