Public IPs#

Pulsewise uses static IP addresses for all outbound monitoring requests. If your infrastructure uses firewalls, security groups, or IP-based access control, you'll need to whitelist these addresses.

When to whitelist#

You need to whitelist Pulsewise's IPs if:

• Your site or servers are behind a firewall that blocks unknown traffic
• You're using Network Path monitoring and need to allow ICMP or TCP probes
• Your web application firewall (WAF) rate-limits or blocks automated requests
• You use IP-based access control on staging or internal sites

IP addresses#

Monitoring servers#

All uptime checks, keyword checks, Lighthouse audits, and network path probes originate from these addresses:

Heartbeat ping endpoint#

Heartbeat pings are received at Pulsewise's web servers. No firewall changes are typically needed for outbound requests from your servers — most firewalls allow outbound HTTPS by default.

Firewall configuration examples#

AWS Security Groups#

Allow inbound traffic from each Pulsewise IP:

Type: Custom TCP
Protocol: TCP
Port Range: 80,443
Source: 52.63.61.99/32

Type: Custom TCP
Protocol: TCP
Port Range: 80,443
Source: 52.77.95.241/32

For Network Path monitoring with ICMP:

Type: Custom ICMP - IPv4
Protocol: ICMP
Port Range: Echo Request
Source: 52.63.61.99/32

Type: Custom ICMP - IPv4
Protocol: ICMP
Port Range: Echo Request
Source: 52.77.95.241/32

iptables#

# Allow Pulsewise monitoring IPs
iptables -A INPUT -s 52.63.61.99/32 -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -s 52.63.61.99/32 -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -s 52.77.95.241/32 -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -s 52.77.95.241/32 -p tcp --dport 443 -j ACCEPT

# For Network Path monitoring (ICMP)
iptables -A INPUT -s 52.63.61.99/32 -p icmp --icmp-type echo-request -j ACCEPT
iptables -A INPUT -s 52.77.95.241/32 -p icmp --icmp-type echo-request -j ACCEPT

Cloudflare#

If you use Cloudflare in front of your origin server, Pulsewise requests arrive through Cloudflare's proxy. You don't need to whitelist Pulsewise IPs in this case, but you may want to create a WAF rule to ensure Pulsewise traffic isn't rate-limited or challenged.

nginx#

# Allow Pulsewise IPs
allow 52.63.61.99;
allow 52.77.95.241;
deny all;

Notifications for IP changes#

Pulsewise IP addresses are static and rarely change. If we ever need to add or change an IP address, we'll notify all customers at least 30 days in advance via email.

Verifying Pulsewise traffic#

To confirm that traffic to your servers is from Pulsewise, check:

1. Source IP — The request should come from one of the IPs listed above.
2. User-Agent — Pulsewise monitoring requests include a Pulsewise/1.0 user agent string.