# Monitoring IPs



VitalSentinel uses the following IP addresses for [Uptime Monitoring](/features/uptime-monitoring) and Custom Pod [Synthetic Monitoring](/features/synthetic-monitoring) tests. If your site is behind a firewall or uses IP-based access controls, you'll need to allowlist these addresses.

<Callout type="info">
  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.
</Callout>

## Current IP Addresses [#current-ip-addresses]

```
194.163.166.126
157.173.116.60
```

**Last updated:** July 14, 2026

## Uptime Bot User Agent [#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 [#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 [#how-to-allowlist]

The process varies depending on your infrastructure:

### Cloudflare [#cloudflare]

1. Go to **Security** → **WAF** → **Tools**
2. Add an IP Access Rule
3. Set Action to **Allow** for each IP

### AWS Security Groups [#aws-security-groups]

1. Go to **EC2** → **Security Groups**
2. Edit inbound rules
3. Add HTTP/HTTPS rules for each IP

### Nginx [#nginx]

Add to your server configuration:

```nginx
allow 194.163.166.126;
allow 157.173.116.60;
```

### Apache [#apache]

Add to your `.htaccess` or virtual host configuration:

```apache
Require ip 194.163.166.126
Require ip 157.173.116.60
```

## Verification [#verification]

After allowlisting, verify VitalSentinel can reach your site:

1. Go to your domain's **Uptime Monitoring** section
2. Check that uptime checks are succeeding
3. Run a **Synthetic Monitoring** test and verify it completes
4. If still failing, verify the IPs are correctly allowlisted

<Callout type="info">
  These IPs may change in the future. We'll notify you via email before any changes to give you time to update your allowlists.
</Callout>

## Related [#related]

<Cards>
  <Card title="Uptime Monitoring" href="/features/uptime-monitoring">
    Availability checks and SSL monitoring
  </Card>

  <Card title="Synthetic Monitoring" href="/features/synthetic-monitoring">
    Lighthouse performance tests
  </Card>

  <Card title="Troubleshooting" href="/help/troubleshooting">
    Solutions to common monitoring issues
  </Card>
</Cards>