Pingdom: IPs & Locations
Verified Pingdom IP Addresses. Copy-Paste Firewall-Setups.
Every official Pingdom 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.
99 IPv4 and 57 IPv6 addresses from probes in 52 cities across 26 countries: 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.
Pingdom 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 Pingdom Monitoring IPs
Pingdom (SolarWinds) publishes live probe lists at my.pingdom.com/probes/ipv4 and /probes/ipv6.
Pingdom, part of SolarWinds, runs one of the largest probe networks in the synthetic monitoring market, with check locations across North America, Europe, and Asia-Pacific. Every uptime check originates from one of its published probe servers.
If your firewall or bot protection blocks these probes, Pingdom records downtime that your real users never saw. Whitelist the full list below. Pingdom probes identify themselves with a user agent containing Pingdom.com_bot.
This list contains 99 IPv4 and 57 IPv6 addresses, verified against the official source on 2026-06-12.
IPv4 addresses 99
- 13.232.220.164
- 23.22.2.46
- 23.83.129.219
- 23.92.127.2
- 23.106.37.99
- 23.111.152.74
- 23.111.159.174
- 43.225.198.122
- 43.229.84.12
- 46.20.45.18
- 46.246.122.10
- 50.16.153.186
- 52.0.204.16
- 52.24.42.103
- 52.48.244.35
- 52.52.34.158
- 52.52.95.213
- 52.52.118.192
- 52.57.132.90
- 52.59.46.112
- 52.59.147.246
- 52.62.12.49
- 52.63.142.2
- 52.63.164.147
- 52.63.167.55
- 52.67.148.55
- 52.73.209.122
- 52.89.43.70
- 52.194.115.181
- 52.197.31.124
- 52.197.224.235
- 52.198.25.184
- 52.201.3.199
- 52.209.34.226
- 52.209.186.226
- 52.210.232.124
- 54.68.48.199
- 54.70.202.58
- 54.94.206.111
- 64.237.49.203
- 64.237.55.3
- 66.165.229.130
- 66.165.233.234
- 72.46.130.18
- 72.46.131.10
- 76.164.234.106
- 76.164.234.130
- 82.103.136.16
- 82.103.139.165
- 82.103.145.126
- 85.195.116.134
- 89.163.146.247
- 89.163.242.206
- 94.75.211.73
- 94.75.211.74
- 94.247.174.83
- 103.47.211.210
- 108.181.70.3
- 141.125.89.147
- 148.72.170.233
- 148.72.171.17
- 151.106.52.134
- 158.175.95.9
- 162.218.67.34
- 162.253.128.178
- 167.17.67.101
- 168.1.203.46
- 169.44.155.138
- 169.51.2.18
- 169.54.70.214
- 169.63.150.216
- 172.241.112.86
- 173.248.147.18
- 174.34.156.130
- 175.45.132.20
- 177.47.99.26
- 178.162.206.244
- 179.50.12.212
- 184.75.210.90
- 184.75.210.226
- 184.75.214.66
- 184.75.214.98
- 185.39.146.214
- 185.39.146.215
- 185.70.76.23
- 185.93.3.65
- 185.136.156.82
- 185.152.65.167
- 185.180.12.65
- 185.246.208.82
- 190.120.230.7
- 196.240.207.18
- 196.244.191.18
- 196.245.151.42
- 199.87.228.66
- 200.58.101.248
- 207.244.80.239
- 209.58.139.193
- 209.58.139.194
IPv6 addresses 57
- 2001:19f0:200:125d::426
- 2001:19f0:200:40cf:225:90ff:fed5:9aea
- 2001:1af8:4400:a056::4052
- 2001:1af8:4400:a056::4053
- 2001:4ba0:ffa5:ed::4003
- 2001:4ba0:ffa5:1d5::4004
- 2001:4ba0:ffe2:22::1
- 2401:c900:1401:71::4078
- 2401:e780:1:91::495
- 2403:f000:1:100:4096:597:1:100
- 2406:da14:48a:7b03::4049
- 2406:da1a:b0a:bf02::4050
- 2600:1f1e:d7c:fd03::4027
- 2600:1f1e:d7c:fd05::4028
- 2604:4500:5:a::4005
- 2604:4500:5:a0::4033
- 2604:4500:8:120::4032
- 2604:4500:9:5d::4031
- 2604:6600:fdc0:12::4066
- 2604:86c0:4001:b::4067
- 2604:b480:fff9::444
- 2604:b480:fffa::4015
- 2605:6f80:0:f::462
- 2605:fe80:2100:a00f:4::4045
- 2605:fe80:2100:a00f:5::4046
- 2606:6080:1001::439
- 2606:6080:1001:1::459
- 2606:6080:1001:4::448
- 2606:9880:f000:4:5::4047
- 2607:f0d0:2601:9b::4211
- 2607:f0d0:3701:f2::4079
- 2607:f0d0:3901:62::4201
- 2607:fc88:100:26::421
- 2804:4c4:dc10:8860::4021
- 2a00:c98:2050:a03a::4086
- 2a00:1a28:2000::4055
- 2a00:9080:1:125::1
- 2a00:9080:1:453::1
- 2a00:9080:2145:e::4048
- 2a01:7a0:2:1754::4056
- 2a01:7a7:2:205c::4058
- 2a01:7a7:2:205d::4057
- 2a02:750:11:284::442
- 2a02:752:100:e::4001
- 2a02:752:100:e::4002
- 2a02:5740:1:11::4076
- 2a02:5740:9:37::4075
- 2a02:5740:21:6::4074
- 2a02:5740:24:14::4073
- 2a02:6ea0:c216::4043
- 2a02:6ea0:c305::4041
- 2a02:6ea0:cb01::4042
- 2a02:6ea0:ce02::4044
- 2a03:8180:1301:146::4070
- 2a03:8180:1801:11::4101
- 2a03:8180:1f01:36::4102
- 2a0d:3002:2100:a00c:5::4065
Last verified: 2026-06-12
Official source: https://documentation.solarwinds.com/en/success_center/pingdom/content/topics/pingdom-probe-servers-ip-addresses.htm
Where Pingdom Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Amsterdam, Netherlands | 94.75.211.74 · 94.75.211.732001:1af8:4400:a056::4053 · 2001:1af8:4400:a056::4052 |
| Athens, Greece | 185.70.76.23NULL |
| Atlanta, United States | 23.111.159.1742604:4500:5:a0::4033 |
| Barcelona, Spain | 108.181.70.32604:6600:fdc0:12::4066 |
| Berlin, Germany | 82.103.145.1262a00:9080:2145:e::4048 |
| Bratislava, Slovakia | 196.245.151.422a02:5740:1:11::4076 |
| Buenos Aires, Argentina | 200.58.101.248 |
| California, United States | 52.52.118.192 · 52.52.34.158 · 52.52.95.213 |
| Chicago, United States | 174.34.156.130NULL |
| Copenhagen, Denmark | 82.103.136.16 · 82.103.139.1652a00:9080:1:453::1 · 2a00:9080:1:125::1 |
| Dallas, United States | 167.17.67.101 · 172.241.112.862604:86c0:4001:b::4067 · 2606:9880:f000:4:5::4047 |
| Denver, United States | 173.248.147.182607:fc88:100:26::421 |
| Dublin, Ireland | 23.92.127.2 · 52.48.244.35 · 52.210.232.124 · 52.209.186.226 · 52.209.34.2262a02:5740:21:6::4074 |
| Düsseldorf, Germany | 89.163.242.206 · 89.163.146.247 · 46.20.45.182001:4ba0:ffa5:01d5::4004 · 2001:4ba0:ffa5:00ed::4003 · 2001:4ba0:ffe2:22::1 |
| Falkenberg, Sweden | 94.247.174.832a02:750:11:284::442 |
| Frankfurt, Germany | 178.162.206.244 · 85.195.116.134 · 52.57.132.90 · 52.59.147.246 · 52.59.46.1122a00:c98:2050:a03a::4086 · 2a01:7a0:2:1754::4056 |
| Helsinki, Finland | 196.244.191.182a02:5740:9:37::4075 |
| Hong Kong, Hong Kong | 43.225.198.122 |
| Las Vegas, United States | 72.46.131.10 · 72.46.130.18NULL · 2605:6f80:0:f::462 |
| London, United Kingdom | 141.125.89.147 · 158.175.95.9 · 23.106.37.992a03:8180:1f01:36::4102 · 2a03:8180:1801:11::4101 · 2a0d:3002:2100:a00c:5::4065 |
| Los Angeles, United States | 66.165.229.1302604:4500:0008:0120::4032 |
| Madrid, Spain | 185.93.3.652a02:6ea0:c305::4041 |
| Matawan, United States | 64.237.49.203 · 64.237.55.32001:19f0:200:40cf:225:90ff:fed5:9aea · 2001:19f0:200:125d::426 |
| Medellin, Colombia | 179.50.12.212NULL |
| Montreal, Canada | 169.54.70.2142607:f0d0:3701:00f2::4079 |
| Mumbai, India | 13.232.220.1642406:da1a:b0a:bf02::4050 |
| New York, United States | 66.165.233.2342604:4500:9:5d::4031 |
| Oregon, United States | 54.70.202.58 · 52.24.42.103 · 52.89.43.70 · 54.68.48.199 |
| Oslo, Norway | 46.246.122.102a00:1a28:2000::4055 |
| Paris, France | 169.51.2.182a03:8180:1301:146::4070 |
| Phoenix, United States | 23.83.129.219NULL |
| Portland, United States | 162.218.67.34 · 199.87.228.662604:b480:fffa::4015 · 2604:b480:fff9::444 |
| Prague, Czech Republic | 185.152.65.1672a02:6ea0:c216::4043 |
| Rio de Janeiro, Brazil | 177.47.99.262804:4c4:dc10:8860::4021 |
| San Francisco, United States | 209.58.139.194 · 209.58.139.1932605:fe80:2100:a00f:5::4046 · 2605:fe80:2100:a00f:4::4045 |
| San Jose, United States | 169.44.155.1382607:f0d0:2601:9b::4211 |
| Santiago, Chile | 190.120.230.7NULL |
| São Paulo, Brazil | 52.67.148.55 · 54.94.206.1112600:1f1e:d7c:fd05::4028 · 2600:1f1e:d7c:fd03::4027 |
| Seattle, United States | 76.164.234.130 · 76.164.234.106NULL · NULL |
| Singapore, Singapore | 43.229.84.12 · 103.47.211.2102401:e780:1:91::495 |
| St. Louis, United States | 148.72.171.17 · 148.72.170.233NULL · NULL |
| Stockholm, Sweden | 185.39.146.214 · 185.39.146.2152a02:752:100:e::4002 · 2a02:752:100:e::4001 |
| Strasbourg, France | 185.136.156.82 · 151.106.52.1342a01:7a7:2:205d::4057 · 2a01:7a7:2:205c::4058 |
| Sydney, Australia | 168.1.203.46 · 52.63.167.55 · 52.62.12.49 · 52.63.164.147 · 52.63.142.2 · 175.45.132.202401:c900:1401:0071::4078 · 2403:f000:1:100:4096:597:1:100 |
| Tampa, United States | 23.111.152.742604:4500:5:a::4005 |
| Tokyo, Japan | 52.194.115.181 · 52.197.31.124 · 52.197.224.235 · 52.198.25.1842406:da14:48a:7b03::4049 |
| Toronto, Canada | 184.75.214.98 · 162.253.128.178 · 184.75.210.226 · 184.75.210.90 · 184.75.214.66NULL · NULL · 2606:6080:1001:1::459 · 2606:6080:1001:4::448 · 2606:6080:1001::439 |
| Vancouver, Canada | 196.240.207.182a02:5740:24:14::4073 |
| Vienna, Austria | 185.180.12.652a02:6ea0:cb01::4042 |
| Virginia, United States | 52.0.204.16 · 50.16.153.186 · 52.201.3.199 · 52.73.209.122 · 23.22.2.46 |
| Warsaw, Poland | 185.246.208.822a02:6ea0:ce02::4044 |
| Washington, United States | 169.63.150.216 · 207.244.80.2392607:f0d0:3901:62::4201 · NULL |
Whitelisting Pingdom-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 13.232.220.164 ufw allow from 23.22.2.46 ufw allow from 23.83.129.219 ufw allow from 23.92.127.2 ufw allow from 23.106.37.99 ufw allow from 23.111.152.74 ufw allow from 23.111.159.174 ufw allow from 43.225.198.122 ufw allow from 43.229.84.12 ufw allow from 46.20.45.18 ufw allow from 46.246.122.10 ufw allow from 50.16.153.186 ufw allow from 52.0.204.16 ufw allow from 52.24.42.103 ufw allow from 52.48.244.35 ufw allow from 52.52.34.158 ufw allow from 52.52.95.213 ufw allow from 52.52.118.192 ufw allow from 52.57.132.90 ufw allow from 52.59.46.112 ufw allow from 52.59.147.246 ufw allow from 52.62.12.49 ufw allow from 52.63.142.2 ufw allow from 52.63.164.147 ufw allow from 52.63.167.55 ufw allow from 52.67.148.55 ufw allow from 52.73.209.122 ufw allow from 52.89.43.70 ufw allow from 52.194.115.181 ufw allow from 52.197.31.124 ufw allow from 52.197.224.235 ufw allow from 52.198.25.184 ufw allow from 52.201.3.199 ufw allow from 52.209.34.226 ufw allow from 52.209.186.226 ufw allow from 52.210.232.124 ufw allow from 54.68.48.199 ufw allow from 54.70.202.58 ufw allow from 54.94.206.111 ufw allow from 64.237.49.203 ufw allow from 64.237.55.3 ufw allow from 66.165.229.130 ufw allow from 66.165.233.234 ufw allow from 72.46.130.18 ufw allow from 72.46.131.10 ufw allow from 76.164.234.106 ufw allow from 76.164.234.130 ufw allow from 82.103.136.16 ufw allow from 82.103.139.165 ufw allow from 82.103.145.126 ufw allow from 85.195.116.134 ufw allow from 89.163.146.247 ufw allow from 89.163.242.206 ufw allow from 94.75.211.73 ufw allow from 94.75.211.74 ufw allow from 94.247.174.83 ufw allow from 103.47.211.210 ufw allow from 108.181.70.3 ufw allow from 141.125.89.147 ufw allow from 148.72.170.233 ufw allow from 148.72.171.17 ufw allow from 151.106.52.134 ufw allow from 158.175.95.9 ufw allow from 162.218.67.34 ufw allow from 162.253.128.178 ufw allow from 167.17.67.101 ufw allow from 168.1.203.46 ufw allow from 169.44.155.138 ufw allow from 169.51.2.18 ufw allow from 169.54.70.214 ufw allow from 169.63.150.216 ufw allow from 172.241.112.86 ufw allow from 173.248.147.18 ufw allow from 174.34.156.130 ufw allow from 175.45.132.20 ufw allow from 177.47.99.26 ufw allow from 178.162.206.244 ufw allow from 179.50.12.212 ufw allow from 184.75.210.90 ufw allow from 184.75.210.226 ufw allow from 184.75.214.66 ufw allow from 184.75.214.98 ufw allow from 185.39.146.214 ufw allow from 185.39.146.215 ufw allow from 185.70.76.23 ufw allow from 185.93.3.65 ufw allow from 185.136.156.82 ufw allow from 185.152.65.167 ufw allow from 185.180.12.65 ufw allow from 185.246.208.82 ufw allow from 190.120.230.7 ufw allow from 196.240.207.18 ufw allow from 196.244.191.18 ufw allow from 196.245.151.42 ufw allow from 199.87.228.66 ufw allow from 200.58.101.248 ufw allow from 207.244.80.239 ufw allow from 209.58.139.193 ufw allow from 209.58.139.194 ufw allow from 2001:19f0:200:125d::426 ufw allow from 2001:19f0:200:40cf:225:90ff:fed5:9aea ufw allow from 2001:1af8:4400:a056::4052 ufw allow from 2001:1af8:4400:a056::4053 ufw allow from 2001:4ba0:ffa5:ed::4003 ufw allow from 2001:4ba0:ffa5:1d5::4004 ufw allow from 2001:4ba0:ffe2:22::1 ufw allow from 2401:c900:1401:71::4078 ufw allow from 2401:e780:1:91::495 ufw allow from 2403:f000:1:100:4096:597:1:100 ufw allow from 2406:da14:48a:7b03::4049 ufw allow from 2406:da1a:b0a:bf02::4050 ufw allow from 2600:1f1e:d7c:fd03::4027 ufw allow from 2600:1f1e:d7c:fd05::4028 ufw allow from 2604:4500:5:a::4005 ufw allow from 2604:4500:5:a0::4033 ufw allow from 2604:4500:8:120::4032 ufw allow from 2604:4500:9:5d::4031 ufw allow from 2604:6600:fdc0:12::4066 ufw allow from 2604:86c0:4001:b::4067 ufw allow from 2604:b480:fff9::444 ufw allow from 2604:b480:fffa::4015 ufw allow from 2605:6f80:0:f::462 ufw allow from 2605:fe80:2100:a00f:4::4045 ufw allow from 2605:fe80:2100:a00f:5::4046 ufw allow from 2606:6080:1001::439 ufw allow from 2606:6080:1001:1::459 ufw allow from 2606:6080:1001:4::448 ufw allow from 2606:9880:f000:4:5::4047 ufw allow from 2607:f0d0:2601:9b::4211 ufw allow from 2607:f0d0:3701:f2::4079 ufw allow from 2607:f0d0:3901:62::4201 ufw allow from 2607:fc88:100:26::421 ufw allow from 2804:4c4:dc10:8860::4021 ufw allow from 2a00:c98:2050:a03a::4086 ufw allow from 2a00:1a28:2000::4055 ufw allow from 2a00:9080:1:125::1 ufw allow from 2a00:9080:1:453::1 ufw allow from 2a00:9080:2145:e::4048 ufw allow from 2a01:7a0:2:1754::4056 ufw allow from 2a01:7a7:2:205c::4058 ufw allow from 2a01:7a7:2:205d::4057 ufw allow from 2a02:750:11:284::442 ufw allow from 2a02:752:100:e::4001 ufw allow from 2a02:752:100:e::4002 ufw allow from 2a02:5740:1:11::4076 ufw allow from 2a02:5740:9:37::4075 ufw allow from 2a02:5740:21:6::4074 ufw allow from 2a02:5740:24:14::4073 ufw allow from 2a02:6ea0:c216::4043 ufw allow from 2a02:6ea0:c305::4041 ufw allow from 2a02:6ea0:cb01::4042 ufw allow from 2a02:6ea0:ce02::4044 ufw allow from 2a03:8180:1301:146::4070 ufw allow from 2a03:8180:1801:11::4101 ufw allow from 2a03:8180:1f01:36::4102 ufw allow from 2a0d:3002:2100:a00c:5::4065
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
Pingdom adds, moves, and retires probe servers regularly. SolarWinds recommends consuming the machine-readable feeds (my.pingdom.com/probes/ipv4 and /probes/ipv6) instead of hardcoding addresses, and re-syncing them periodically.
Pingdom uptime probes send a user agent containing "Pingdom.com_bot". Use it to identify probe traffic in your logs, but enforce access by IP, not by user agent.
Yes. Pingdom publishes a separate IPv6 probe list. Whitelist both lists if your site is dual-stacked.
The most common cause is a WAF, geo-block, or rate limiter blocking probe IPs from certain regions. Whitelisting the full probe list removes that entire class of false positives.
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 Pingdom and are published by Pingdom 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 Pingdom. 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.