What is New Relic?
Direct Answer: New Relic bot, operated by New Relic, monitors customer applications for availability and performance issues.
The New Relic bot is used by New Relic's Intelligent Observability Platform to monitor customer applications for availability and performance issues. It does so with a user-agent string of 'Mozilla/5.0 (compatible; NewRelicbot/2.1; +http://www.newrelic.com)'. The bot's behavior is designed to support the platform's monitoring capabilities.
User-Agent Identification
The following user-agent strings identify New Relic in your live traffic data:
Mozilla/5.0 (compatible; NewRelicbot/2.1; +http://www.newrelic.com)
robots.txt Rules for New Relic
Respects robots.txt: No
This bot does not commit to following robots.txt
New Relic does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.
Need continuous verification across 500+ bots? Can AI See It automates this.
Crawl Behavior
Frequency:Continuous
Request Pattern:Not Documented
Crawl Activity Index
Relative crawl activity for New Relic over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.
View recent activity data (last 7 days)
| Date | Activity Index |
|---|---|
| Mar 26, 2026 | 88.0 |
| Mar 27, 2026 | 82.7 |
| Mar 28, 2026 | 83.1 |
| Mar 29, 2026 | 81.8 |
| Mar 30, 2026 | 87.3 |
| Mar 31, 2026 | 90.2 |
| Apr 1, 2026 | 88.8 |
Source: Cloudflare Radar
Why track New Relic traffic?
Distinguish monitoring traffic from real crawler activity. New Relic checks your site availability at regular intervals. Without proper identification, these requests can inflate your bot traffic metrics and distort crawl analysis.
Validate monitoring coverage. Track which pages New Relic checks and how frequently, so your monitoring setup matches your infrastructure requirements.
Log Verification
To verify New Relic traffic in your live traffic data:
- Search access logs for the user-agent strings listed above
- Check if the IP addresses match documented ranges (if provided by New Relic)
- Verify the crawl pattern matches documented behavior
- Use reverse DNS lookup for additional verification if available
Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.
Undocumented Information
The following information is not officially documented for New Relic:
- crawl frequency details
- request pattern
- JavaScript rendering details
- IP verification URL
Official Documentation
View Official New Relic Documentation →
Information sourced from official documentation. Content generated with AI assistance.