Pingdom IP ranges
Current IP ranges (CIDRs) used by the Pingdom monitoring network, updated daily.
| category | Uptime Monitoring |
|---|---|
| website | https://www.pingdom.com |
| ranges | 206 (149 IPv4, 57 IPv6) |
| last change | |
| downloads | 676 |
| download | txt csv json — permalinks, always the latest data |
curl -O https://cloud-ip-ranges.com/download/pingdom.txt
Ranges
Sample of 25 of 206 ranges. Download the full list above, or check a specific IP.
| CIDR | Type |
|---|---|
| 3.10.222.182/32 | ipv4 |
| 3.11.131.95/32 | ipv4 |
| 3.66.99.59/32 | ipv4 |
| 3.120.200.34/32 | ipv4 |
| 3.121.108.101/32 | ipv4 |
| 3.125.198.20/32 | ipv4 |
| 3.127.78.190/32 | ipv4 |
| 3.219.128.11/32 | ipv4 |
| 3.234.196.132/32 | ipv4 |
| 13.41.140.26/32 | ipv4 |
| 13.41.156.80/32 | ipv4 |
| 13.48.152.99/32 | ipv4 |
| 13.49.128.195/32 | ipv4 |
| 2001:19f0:200:125d::426/128 | ipv6 |
| 2001:19f0:200:40cf:225:90ff:fed5:9aea/128 | ipv6 |
| 2001:1af8:4400:a056::4052/128 | ipv6 |
| 2001:1af8:4400:a056::4053/128 | ipv6 |
| 2001:4ba0:ffa5:ed::4003/128 | ipv6 |
| 2001:4ba0:ffa5:1d5::4004/128 | ipv6 |
| 2001:4ba0:ffe2:22::1/128 | ipv6 |
| 2401:c900:1401:71::4078/128 | ipv6 |
| 2401:e780:1:91::495/128 | ipv6 |
| 2403:f000:1:100:4096:597:1:100/128 | ipv6 |
| 2406:da14:48a:7b03::4049/128 | ipv6 |
| 2406:da1a:b0a:bf02::4050/128 | ipv6 |
Blocking Pingdom
iptables
curl -sO https://cloud-ip-ranges.com/download/pingdom.txt
while read ip; do
iptables -A INPUT -s $ip -j DROP
iptables -A OUTPUT -d $ip -j DROP
done < pingdom.txt
ufw
curl -sO https://cloud-ip-ranges.com/download/pingdom.txt
while read ip; do
ufw deny from $ip
ufw deny to $ip
done < pingdom.txt
fail2ban
sudo tee /etc/fail2ban/filter.d/pingdom-block.conf << EOF
[Definition]
failregex = ^.*$
ignoreregex =
EOF
sudo tee /etc/fail2ban/jail.d/pingdom-block.conf << EOF
[pingdom-block]
enabled = true
filter = pingdom-block
action = iptables-allports[name=pingdom]
logpath = /tmp/pingdom.txt
findtime = 1
bantime = -1
maxretry = 1
EOF
curl -so /tmp/pingdom.txt https://cloud-ip-ranges.com/download/pingdom.txt
sudo systemctl restart fail2ban
pfSense / OPNsense
curl -sO https://cloud-ip-ranges.com/download/pingdom.txt
# Firewall > Aliases: new alias PINGDOM_BLOCK, type Network(s), import the file
# Firewall > Rules > WAN: Action=Block, Source=PINGDOM_BLOCK
About
These are the addresses Pingdom's uptime checks run from, updated regularly from its official list. Most people allowlist them so monitoring isn't rate-limited or blocked by a WAF; the same list also lets you identify Pingdom probes in your access logs, or block monitoring you didn't ask for. Last update was about 12 hours ago.
Other providers
AirVPN, Akamai, Alibaba, Alpha Strike Labs, Amazonbot, Amzn-SearchBot, Amzn-User, Anthropic, AppleBot, Atlassian, AWS, Azure, Backblaze, Baidu, BinaryEdge, BingBot, Bunny, CacheFly, CCBot, Censys, ChatGPT-User, ClaudeBot, Cloudflare, Datadog, DigitalOcean, DuckDuckBot, Fastly, Gabia, G-Core, GitHub, Googlebot, Google Cloud, Google Public DNS, Google Services, GPTBot, Hetzner, Hostway, Huawei Cloud, IBM Cloud, iCloud Private Relay, Internet Archive, IVPN, Leaseweb, Linode, Meta, Microsoft 365, Mistral, Mullvad, NHN Cloud, NordVPN, OpenAI ChatGPT, OpenAI SearchBot, Oracle Cloud, OVHcloud, OVPN.com, PerplexityBot, Perplexity-User, Private Internet Access, QUIC.cloud, Rackspace, Rapid7 Sonar, Salesforce, Scaleway, Shodan, StatusCake, StormWall, Stretchoid, Sucuri, Telegram, Tencent, TOR, UpCloud, UptimeRobot, Vultr, Wasabi, Windscribe, Yandex, Zoho, Zoom, Zscaler