Pingdom
Pingdom is a developer or operator tool operated by Pingdom. It runs on behalf of a site owner for monitoring, uptime checks, performance audits, or internal QA.
If you run the site, you are probably the customer of whoever is running this agent. Blocking it would hide your own monitoring data from yourself.
If you are an end-user surprised to see this in your logs, it is almost always something a third-party SaaS is doing on behalf of someone who manages your site.
See Pingdom on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
User-Agent only
Crawl frequency
Scheduled probes
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Pingdom runs 2 bots in total. Each one is a separate user-agent so you can allow or block them independently.
DevOps & Monitoring
2- PingdomYou are here
- Pingdom TMS (Transaction Monitor)
Share of AI bot traffic
0.60%
↑ 50% vs 12 mo ago
% of top sites blocking it
0.90%
↑ 50% vs 12 mo ago
Top page categories crawled
DevOps & Monitorings as a category, share of all bot traffic
2.0%
↑ 43% vs 12 mo ago
Sum of every devops & monitoring we have public stats on. Compare to Pingdom's individual trend above to see if it's pulling ahead of its category or falling behind.
Crawl-to-click ratio
No referrals
This agent does not send referral traffic back. Cloudflare crawl-to-click data
Snapshot updated
2026-04
Connect Agent Analytics for daily, per-site numbers.
Should I let Pingdom through?
In most cases, yes. Almost always run by you or your vendor. Blocking hides your own monitoring data. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Pingdom affect my Google rankings?
No. Pingdom is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from Pingdom?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be Pingdom", not "the traffic is genuinely Pingdom". If you need stronger guarantees, look for a reverse-DNS check or wait for Pingdom to publish IP ranges.
What's the best way to understand what Pingdom is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
How is Pingdom different from Pingdom's other bots?
Pingdom splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Pingdom family above to see which ones actually matter for your site.
What's the cleanest way to control Pingdom?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.