Monitoring bot
New Relic Pinger
Uptime and performance checks. Usually configured by you or your own tools.
Last updated
At a glance
| Category | Monitoring bot |
|---|---|
| User agent match | contains "newrelicpinger" |
| Executes JavaScript | No |
| Respects robots.txt | No |
| Identity verifiable | No, the name is only a claim |
| IVT class | GIVT (general invalid traffic: declared automation) |
What New Relic Pinger is
New Relic Pinger performs uptime or performance checks. Traffic from it almost always exists because somebody configured it: you, your host, your agency, or a service you signed up for. It is declared automation and is filtered out of your human numbers.
Can the name be trusted?
There is no published way to verify New Relic Pinger: the operator provides no IP ranges and no reverse DNS scheme, so the name in the user agent is only a claim. Any script can send it. TrueVisit still names the traffic, and weighs the claim against behavioral signals instead of trusting it.
Should you block it?
Blocking New Relic Pinger usually breaks your own alerting: the monitor reports your site as down and someone gets paged at 3am for a wall you built yourself. Find out who configured it before touching it. If genuinely nobody on your side did, treat it as unwanted automation and block away.
How TrueVisit reports it
Visits from New Relic Pinger appear in your bot report under this exact name, never as an anonymous percentage, and every verdict stores the reason it was reached. Because this client never executes JavaScript, a browser-only tracker cannot see it at all; it is visible through server-side collection, which is how the visits reach your report.