Monitoring IPs
IP addresses used by VitalSentinel for Uptime and Synthetic Monitoring.
VitalSentinel uses the following IP addresses for Uptime Monitoring and Custom Pod Synthetic Monitoring tests. If your site is behind a firewall or uses IP-based access controls, you'll need to allowlist these addresses.
Synthetic tests that run from the default Google's Servers location use Google's PageSpeed Insights infrastructure, not these IPs. The addresses below cover uptime checks and Custom Pod synthetic tests.
Current IP Addresses
194.163.166.126
157.173.116.60Last updated: July 14, 2026
Uptime Bot User Agent
Uptime checks are sent with the following User-Agent string, which you can also match in firewall or WAF rules:
VitalSentinel Uptime Bot/1.0 (+https://www.vitalsentinel.com/uptime-bot)When to Allowlist
You may need to allowlist these IPs if:
- Your site is behind a firewall that blocks unknown traffic
- You use a web application firewall (WAF) with strict rules
- Your hosting provider restricts access by IP
- You have rate limiting that might block monitoring requests
How to Allowlist
The process varies depending on your infrastructure:
Cloudflare
- Go to Security → WAF → Tools
- Add an IP Access Rule
- Set Action to Allow for each IP
AWS Security Groups
- Go to EC2 → Security Groups
- Edit inbound rules
- Add HTTP/HTTPS rules for each IP
Nginx
Add to your server configuration:
allow 194.163.166.126;
allow 157.173.116.60;Apache
Add to your .htaccess or virtual host configuration:
Require ip 194.163.166.126
Require ip 157.173.116.60Verification
After allowlisting, verify VitalSentinel can reach your site:
- Go to your domain's Uptime Monitoring section
- Check that uptime checks are succeeding
- Run a Synthetic Monitoring test and verify it completes
- If still failing, verify the IPs are correctly allowlisted
These IPs may change in the future. We'll notify you via email before any changes to give you time to update your allowlists.