Pingdom Bot

Operator

SolarWinds (Pingdom)

Type

Site Monitor

Official page

documentation.solarwinds.com

Published IP ranges

my.pingdom.com/probes/ipv4

In Vireo

Excluded, reported under Uptime monitors

What it does

Runs Pingdom's monitoring checks (uptime, page speed and transaction checks) against sites its customers monitor.

Pingdom has different services and the behavior in triggering various analytics on your site will differ.

SolarWinds (Pingdom)

User agent

Requests from Pingdom Bot carry user agents like these:

Pingdom.com_bot_version_1.4_(http://www.pingdom.com/)

Mozilla/5.0 (Unknown; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) PingdomTMS/0.8.5 Safari/534.34

Device Detector identifies it with this pattern (a case-insensitive regular expression):

Pingdom(?:\.com|TMS)

Anyone can put any name in a user agent. Where the operator publishes IP ranges, checking the request's address against them is the way to confirm a visit is genuine.

Worth knowing

Behavior depends on check type. Uptime checks don't run JavaScript. Page speed and transaction checks use a real Chrome browser, run from AWS, and show up in analytics. The docs say to filter on 'pingdom' in the user agent. IPv6 and RSS lists are also published.

Page Speed Checks will trigger analytics, the tests are done using a real chrome browser.

SolarWinds (Pingdom)

How Vireo counts Pingdom Bot

Vireo keeps requests from Pingdom Bot out of your pageviews and visitors and counts them on its bot report under Uptime monitors, so you can see how much it left out rather than wonder why your server logs show more traffic.

Checked by running Vireo Analytics' own bot filter over Pingdom Bot's user agents.

Sources

• SolarWinds (Pingdom): crawler documentation (checked October 2026)
• Matomo Device Detector, bots.yml (LGPL-3.0)