Pingdom IP Ranges
Pingdom, the uptime and page-speed monitor owned by SolarWinds, checks a site from probe servers around the world and publishes the list of their addresses. On 16 October 2026 it held 149 single IPv4 addresses. What sets the list apart is how scattered it is: the probes sit on 37 different networks, deliberately, so that a check from one place is not affected by the same outage as a check from another.
- Provider
- Pingdom
- Hosting network
- AS16509 Amazon and 36 other networks
- Category
- Monitoring
- Headquarters
- Austin, TX, USA (SolarWinds)
- Published IPv4 prefixes
- 149
- Registry
- Self-published list
Known IP ranges
Pingdom has no network of its own. These are the probe addresses it publishes at my.pingdom.com/probes/ipv4, as fetched on 2026-10-16: 149 single hosts. They are spread across 37 different networks - Amazon carries 80, IBM Cloud 7, and the rest are one to five probes each at hosting companies across the world. WHOIS on any of them names the host; the list is what says it is Pingdom.
3.10.222.182/32
3.11.131.95/32
3.66.99.59/32
3.120.200.34/32
3.121.108.101/32
3.125.198.20/32
3.127.78.190/32
3.219.128.11/32
3.234.196.132/32
13.41.140.26/32
What does a Pingdom IP mean in a privacy test?
A Pingdom address in an access log is a monitor checking the page, not a visitor and not a VPN exit. If those requests are being blocked, Pingdom reports downtime or slow responses that real visitors never see.
149 probes on 37 networks
Every address was checked against the routing table on 16 October 2026. Amazon announces 80 of them - 69 on AS16509 and 11 on AS14618. IBM Cloud's AS36351 announces 7. After that the list fans out: Glesys, CDN77, WIIT, Asergo, LeaseWeb and twenty-nine more hosting networks carry between one and five probes each.
That spread is a design choice for monitoring - an outage at one host takes out a few probes, not the service - but it makes network-level rules useless. There is no ASN to allow, and allowing 37 of them would admit a large share of the world's rented servers.
Allowing probes without allowing everything
Exempt the listed addresses, individually, ahead of any rule that blocks data-center traffic. The list is published in more than one form - this page uses the plain IPv4 list - and Pingdom changes it as probes are added or retired, so a copied rule needs refreshing.
The probes also send a Pingdom user-agent. On its own that proves nothing, since anyone can send it; together with an address from the list, it is a reliable sign of a real check.
Related tools
Frequently asked questions
What IP addresses does Pingdom use?
The 149 IPv4 probe addresses at my.pingdom.com/probes/ipv4, checked on 16 October 2026. They are single hosts spread across 37 networks.
Why does a Pingdom IP appear in my logs or a privacy test?
A Pingdom address in an access log is a monitor checking the page, not a visitor and not a VPN exit. If those requests are being blocked, Pingdom reports downtime or slow responses that real visitors never see.
Why does Pingdom report downtime when my site is up?
A common cause is a firewall or WAF blocking some of its probes. They run on data-center networks, which bot rules often block. Exempt the published addresses before those rules.
Does Pingdom have its own ASN?
No. Its probes are rented servers: 80 on Amazon's networks, 7 on IBM Cloud and the rest on 34 other hosting networks, as checked on 16 October 2026.
Can I allowlist Pingdom by ASN?
No. There are 37 networks behind the 149 probes, all shared with other customers. Allowlist the addresses themselves.