Which user-agent strings identify Server Density?

The following user-agent strings identify Server Density: Server Density Service Monitoring v2, Server Density Agent.

Does Server Density respect robots.txt rules?

According to official documentation, Server Density does not respect robots.txt rules.

How can I verify Server Density traffic with live traffic data?

You can verify Server Density requests by checking your server access logs for the documented user-agent strings. For accurate verification, correlate user-agent patterns with IP ranges or verification methods provided by Stackpath.

What is Server Density?

Direct Answer: Server Density bot by Stackpath for proactive infrastructure monitoring

Operator: Stackpath Type: Monitoring Bot Purpose: Proactive infrastructure monitoring

The Server Density bot, operated by Stackpath, is used for proactive infrastructure monitoring of cloud, servers, containers, and websites. It appears to be a monitoring tool aimed at providing insights into the performance and status of various digital assets.

User-Agent Identification

The following user-agent strings identify Server Density in your live traffic data:

Server Density Service Monitoring v2
Server Density Agent

robots.txt Rules for Server Density

Respects robots.txt: No

This bot does not commit to following robots.txt

Server Density 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:Not Documented

Request Pattern:Not Documented

Crawl Activity Index

Relative crawl activity for Server Density 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 Server Density traffic?

Distinguish monitoring traffic from real crawler activity. Server Density 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 Server Density checks and how frequently, so your monitoring setup matches your infrastructure requirements.

Log Verification

To verify Server Density 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 Stackpath)
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 Server Density:

crawl frequency
IP verification
JavaScript rendering
user-agent variations

Official Documentation

View Official Server Density Documentation →

Information sourced from official documentation. Content generated with AI assistance.