Bot intelligence record
NewRelicPinger
Review firstNewRelicPinger is a monitoring bot from New Relic used for uptime monitoring, synthetic checks, performance measurement, accessibility review; it appears in server logs as `NewRelicPinger`.
- Operator
- New Relic
- Family
- New Relic
- Type
- Monitoring Bot
- Source type
- Observed
- Last checked
- 2026-06-22
User-Agent Pattern
New RelicNewRelicPinger
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: NewRelicPinger
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
AllowUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
NewRelicPinger is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Record Details
Structured data- Operator
- New Relic
- Family
- New Relic
- Type
- Monitoring Bot
- Purpose
- Uptime And Performance Monitoring
- Identity type
- Documented
- Confidence
- Medium
- Last verified
- 2026-06-22
- Last checked
- 2026-06-22
- Source type
- Observed
- Verification
- Verify NewRelicPinger by matching `NewRelicPinger` to New Relic evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- NewRelicPinger has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- NewRelicPinger is a monitoring bot from New Relic used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Its primary user-agent pattern is
NewRelicPinger. - NewRelicPinger is verified with Medium confidence. The identity type is Documented, and the evidence basis is observed traffic patterns and user-agent evidence.
- NewRelicPinger does not have confirmed robots.txt behavior in the available public evidence.
- NewRelicPinger can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify NewRelicPinger by matching `NewRelicPinger` to New Relic evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- NewRelicPinger traffic is primarily detected by the `NewRelicPinger` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with New Relic infrastructure before trusting the traffic.
- NewRelicPinger is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- NewRelicPinger has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.