UptimeMatrix User-Agent for Monitoring Requests
This page documents the official UptimeMatrix monitoring User-Agent. The User-Agent is used for website and service monitoring requests and helps site owners identify legitimate monitoring traffic.
All monitoring requests are clearly identified with a standardized user agent string that includes version information, regional identification, and a reference to this documentation.
Note: This User-Agent is fixed and should not be modified.
User Agent String Format
Format used by all UptimeMatrix monitoring agents
Why This User-Agent Exists
Monitoring systems need a consistent identifier to distinguish monitoring traffic from bots and other automated systems. The UptimeMatrix User-Agent provides:
- •Clear identification: Helps distinguish monitoring traffic from bots and crawlers
- •Security allowlisting: Used by security teams for allowlisting legitimate monitoring requests in WAFs and firewalls
- •Transparency: Makes monitoring requests easily identifiable in server logs and analytics
Dynamic Version & Region
The user agent string includes two dynamic components:
- •Version (currently
1.0): Updated with each agent release - •Region (e.g., SG, US, EU): Dynamically set based on the monitoring station location
User Agent String Breakdown
Mozilla/5.0
Historical compatibility string for maximum compatibility with web servers and applications
compatible
Indicates this is a compatible user agent, not a browser
UptimeMatrix/1.0
Product name and version identifier. Version (currently 1.0) is updated with each agent release.
region={REGION}
Dynamic region code indicating the monitoring station location (e.g., SG, US, EU, JP, AU, GB, DE, FR)
+https://uptimematrix.com/agent
Reference URL pointing to this documentation page for identification and contact information
Key Features
Our user agent implementation provides transparency and ease of identification
Transparent Identification
Clear product identification allows webmasters to identify and manage monitoring traffic appropriately
Regional Transparency
Dynamic region code provides visibility into which monitoring location performed each check
Documentation Link
Includes reference URL to this page for easy access to documentation and contact information
Version Tracking
Version number enables tracking of agent updates and compatibility across different deployments
Compatibility
Uses standard format that ensures maximum compatibility with web servers and applications
Best Practices
Follows industry best practices for user agent strings and ethical monitoring practices
Common Use Cases
How website owners and administrators can use the UptimeMatrix user agent for various purposes
Common scenarios: Allowlisting in WAFs (Cloudflare, AWS WAF, etc.), firewall rule exceptions, bot filtering verification, and debugging false positives.
Server Log Identification
Identify UptimeMatrix monitoring requests in your server logs and analytics tools
Access Control
Whitelist or recognize legitimate monitoring traffic in firewall rules and security policies
Analytics Filtering
Filter out monitoring traffic from your website analytics to get accurate visitor data
Rate Limiting
Apply appropriate rate limiting policies for monitoring agents vs regular visitors
Traffic Analysis
Analyze monitoring patterns and distinguish legitimate monitoring from potential threats
Compliance & Audit
Document monitoring activities and maintain compliance with security policies
Technical Specifications
Detailed technical information about the user agent format
Format Structure
Standard user agent format with product identifier, version, region code, and documentation URL
Version Management
Version number (currently 1.0) is updated with each agent release to track compatibility and changes
Regional Identification
Region code dynamically identifies the monitoring station location using standard country/region codes
Compatibility
Uses widely recognized format ensuring maximum compatibility with web servers, proxies, and CDNs
Benefits of Proper User Agent Identification
Transparency
Clear identification of monitoring traffic helps website owners understand their visitors
Security
Allows proper whitelisting and reduces false positives in security monitoring systems
Analytics Accuracy
Enables filtering of monitoring traffic from visitor analytics for accurate metrics
Compliance
Proper identification helps meet compliance requirements for traffic logging and audit trails
Debugging
Makes it easier to identify and troubleshoot monitoring-related issues in server logs
Best Practices
Follows industry best practices for user agent strings and monitoring ethics
Regional Tracking
Region codes help identify which monitoring location performed each check
Version Control
Version tracking helps identify agent updates and maintain compatibility
Monitoring Regions
UptimeMatrix monitoring agents operate from multiple global locations. The region code in the user agent dynamically identifies the monitoring location.
Current Agent Version: 1.0
Preview with Selected Region
Monitoring from 63+ locations worldwide for comprehensive coverage
How to Identify UptimeMatrix Traffic
Examples of how to filter or identify UptimeMatrix monitoring requests in various systems
Apache Access Log
Nginx Access Log
Regular Expression Pattern
Cloudflare Workers / Edge Functions
Google Analytics Filter
Frequently Asked Questions
Why does UptimeMatrix use a custom user agent?
Using a custom user agent allows website owners to easily identify monitoring traffic, filter it from analytics, whitelist it in security systems, and maintain compliance with traffic logging requirements. It follows industry best practices for transparency and ethical monitoring.
How does the dynamic region work?
The region code in the user agent string is automatically set based on the monitoring station location that performs each check. For example, checks from Singapore use region=SG, while checks from the United States use region=US. This allows you to identify which geographic location performed each monitoring check in your server logs.
Will the version number change?
Yes, the version number (currently 1.0) is updated with each agent release to reflect changes, improvements, and new features. This allows webmasters to track which version of the monitoring agent is performing checks and helps with compatibility tracking and troubleshooting.
Can I block UptimeMatrix monitoring requests?
While technically possible, blocking UptimeMatrix requests would prevent monitoring from working. If you have concerns about monitoring traffic or need to implement custom filtering, please contact our support team to discuss alternatives or custom configurations. We're committed to working with website owners to ensure monitoring is performed in a way that respects their preferences.
How often does UptimeMatrix check my website?
Check frequency depends on your monitoring plan. The minimum interval is typically 1 minute, and you can configure intervals up to 24 hours. Multiple monitoring locations may perform checks from different regions, which is why the region code in the user agent helps identify the source of each check.
What should I do if I see suspicious requests claiming to be UptimeMatrix?
Always verify requests match the exact format shown on this page: Mozilla/5.0 (compatible; UptimeMatrix/1.0; region=XX; +https://uptimematrix.com/agent). If you encounter requests that don't match this format or seem suspicious, please report them to our security team immediately at [email protected].
Security & Trust Notes
Transparent identification: UptimeMatrix does not impersonate browsers. The User-Agent clearly identifies monitoring requests and includes a reference URL to this documentation page.
Identifiable requests: The User-Agent is transparent and identifiable, making it easy for site owners to distinguish legitimate monitoring traffic from other automated systems.
Monitoring purposes only: Requests using this User-Agent are for monitoring purposes only. They verify availability, check response times, and validate service health.
Related Monitoring Documentation
Additional resources for monitoring and understanding HTTP requests
Website Monitoring
Monitor website availability and HTTP responses
API Monitoring
Track API endpoints and status codes
Network Monitoring
Monitor network performance and connectivity
Support
Get help with monitoring and User-Agent questions
Documentation
Complete monitoring documentation and guides
HTTP Status Codes
Reference guide for HTTP response codes