Resource

Complete Guide to Pulse Stack™ Monitoring Server IPs

Why You Need Our Server IP Addresses

When Pulse Stack™ monitors your websites and applications, our distributed network of servers sends regular health check requests. Some hosting providers and firewalls may block these legitimate monitoring requests, causing false downtime alerts.

To ensure accurate monitoring results, you'll need to configure your security systems to accept traffic from our monitoring infrastructure. This page provides all the necessary IP addresses and configuration guidance.

Access Methods for IP Lists

We provide multiple convenient ways to obtain our current monitoring server IP addresses:

  • API Endpoint: ip.pulsestack.co.uk (returns JSON format)
  • IPv4 Text File: Plain text format for easy importing
  • Combined IPv4/IPv6 File: All addresses in one download
  • DNS Query: Programmatically retrieve the latest IPs

Important Notice: Our monitoring infrastructure undergoes regular updates. We recommend using our API endpoint to ensure you always have the most current IP addresses for your firewall rules.

2.7M+
Users worldwide
7.5M+
Monitors active
99.9%
Platform uptime
<2min
Avg support response

How Our Global Monitoring Network Operates

Pulse Stack™ employs a sophisticated multi-layered monitoring approach across four continental regions. Initial health checks originate from randomly selected servers within the same geographical area as your monitored service.

When potential issues are detected, our system immediately triggers verification checks from multiple independent servers and providers in the region. This methodology significantly reduces false positive alerts whilst maintaining rapid response times for genuine outages.

IPv4 Monitoring Server Addresses

North American Servers

3.212.128.62, 34.198.201.66, 52.22.236.30, 54.167.223.174, 52.87.72.16, 54.87.112.51, 3.20.63.178, 52.15.147.27, 3.12.251.153, 18.116.205.62, 3.133.226.214, 3.149.57.90, 45.55.123.175, 45.55.127.146, 129.212.132.140, 134.199.240.137, 138.197.53.117, 138.197.53.138, 138.197.54.143, 138.197.54.247, 138.197.63.92, 143.244.221.177, 144.126.251.21, 209.38.49.1, 209.38.49.206, 209.38.49.226, 209.38.51.43, 5.161.75.7, 5.161.73.160, 5.161.113.195, 5.161.117.52, 5.161.177.47, 5.161.194.92, 5.161.215.244, 178.156.181.172, 178.156.184.20, 178.156.185.127, 178.156.185.231, 178.156.187.238, 178.156.189.113, 178.156.189.249, 69.162.124.227, 69.162.124.235, 69.162.124.238, 216.144.248.18, 216.144.248.19, 216.144.248.21, 216.144.248.22, 216.144.248.23, 216.144.248.24, 216.144.248.25, 216.144.248.26, 216.144.248.27, 216.144.248.28, 216.144.248.29, 216.144.248.30, 216.245.221.83

European Servers

3.77.67.4, 3.79.134.69, 18.192.166.72, 18.193.252.127, 52.28.162.93, 52.59.43.236, 63.178.84.147, 24.144.78.39, 24.144.78.185, 64.225.81.248, 64.225.82.147, 143.198.249.237, 143.198.250.89, 143.244.196.21, 143.244.196.211, 152.42.149.135, 159.223.243.219, 161.35.247.201, 167.99.18.52, 188.166.201.79, 206.189.241.133, 209.38.53.7, 49.13.24.81, 49.13.130.29, 49.13.134.145, 78.47.98.55, 88.99.80.227, 142.132.180.39, 157.90.155.240, 157.90.156.63, 168.119.53.160, 168.119.96.239, 49.13.164.148, 49.13.167.123, 78.46.190.63, 78.47.173.76, 128.140.41.193, 128.140.106.114, 159.69.158.189, 167.235.143.113, 168.119.123.75, 78.46.215.1, 91.99.101.207

Asia-Pacific Servers

18.180.208.214, 54.64.67.106, 54.249.170.27, 139.59.50.44, 146.190.9.187, 209.38.124.252, 5.223.43.32, 5.223.53.147, 5.223.57.22

Australian Servers

3.105.133.239, 3.105.190.221, 54.79.28.129, 170.64.250.64, 170.64.250.132, 170.64.250.235

Ready to put this into practice?

Start monitoring your infrastructure today.

Get started

IPv6 Monitoring Server Addresses

North American IPv6 Servers

2600:1f18:179:f900:4b7d:d1cc:2d10:211, 2600:1f18:179:f900:4696:7729:7bb3:f52f, 2600:1f18:179:f900:5c68:91b6:5d75:5d7, 2600:1f18:179:f900:71:af9a:ade7:d772, 2600:1f18:179:f900:2406:9399:4ae6:c5d3, 2600:1f18:179:f900:e8dd:eed1:a6c:183b, 2600:1f16:775:3a00:8c2c:2ba6:778f:5be5, 2600:1f16:775:3a00:dbbe:36b0:3c45:da32, 2600:1f16:775:3a00:37bf:6026:e54a:f03a, 2600:1f16:775:3a00:ac3:c5eb:7081:942e, 2600:1f16:775:3a00:3f24:5bb0:95d7:5a6b, 2600:1f16:775:3a00:91ac:3120:ff38:92b5, 2604:a880:800:14:0:1:68ba:d000, 2604:a880:800:14:0:1:68ba:e000, 2604:a880:800:14:0:1:68bb:0, 2604:a880:800:14:0:1:68bb:1000, 2604:a880:800:14:0:1:68bb:3000, 2604:a880:800:14:0:1:68bb:4000, 2604:a880:800:14:0:1:68bb:5000, 2604:a880:800:14:0:1:68bb:6000, 2604:a880:800:14:0:1:68bb:7000, 2604:a880:800:14:0:1:68bb:a000, 2604:a880:800:14:0:1:68bb:b000, 2604:a880:800:14:0:1:68bb:c000, 2604:a880:800:14:0:1:68bb:d000, 2604:a880:800:14:0:1:68bb:e000, 2604:a880:800:14:0:1:68bb:f000

European IPv6 Servers

2a05:d014:1815:3400:6d:9235:c1c0:96ad, 2a05:d014:1815:3400:90b4:4ef9:5631:b170, 2a05:d014:1815:3400:654f:bd37:724c:212b, 2a05:d014:1815:3400:9779:d8e9:100a:9642, 2a05:d014:1815:3400:af29:e95e:64ff:df81, 2a05:d014:1815:3400:c7d6:f7f3:6cc1:30d1, 2a05:d014:1815:3400:d784:e5dd:8e0:67cb, 2a03:b0c0:2:f0::bd91:f001, 2a03:b0c0:2:f0::bd92:1, 2a03:b0c0:2:f0::bd92:1001, 2a03:b0c0:2:f0::bd92:2001, 2a03:b0c0:2:f0::bd92:4001, 2a03:b0c0:2:f0::bd92:5001, 2a03:b0c0:2:f0::bd92:6001, 2a03:b0c0:2:f0::bd92:7001, 2a03:b0c0:2:f0::bd92:8001, 2a03:b0c0:2:f0::bd92:9001, 2a03:b0c0:2:f0::bd92:a001, 2a03:b0c0:2:f0::bd92:b001, 2a03:b0c0:2:f0::bd92:c001, 2a03:b0c0:2:f0::bd92:e001, 2a03:b0c0:2:f0::bd92:f001

Asia-Pacific IPv6 Servers

2406:da14:94d:8601:9d0d:7754:bedf:e4f5, 2406:da14:94d:8601:b325:ff58:2bba:7934, 2406:da14:94d:8601:db4b:c5ac:2cbe:9a79, 2400:6180:100:d0::94b6:4001, 2400:6180:100:d0::94b6:5001, 2400:6180:100:d0::94b6:7001

Firewall Configuration Examples

Below are practical examples for configuring popular firewall systems to accept Pulse Stack™ monitoring traffic:

Windows Defender Configuration

Creating Allow Rules:

  1. Open Windows Defender Firewall with Advanced Security
  2. Select 'Inbound Rules' and click 'New Rule'
  3. Choose 'Custom' rule type and proceed
  4. Select 'All Programs' and continue
  5. Under 'Protocol and Ports', keep defaults and proceed
  6. In 'Scope', add Pulse Stack™ IPs to 'These IP addresses'
  7. Choose 'Allow the connection'
  8. Apply to all network profiles and provide a descriptive name

Linux iptables Commands

Accepting Traffic from Monitoring IPs:

sudo iptables -A INPUT -s [IP_ADDRESS] -j ACCEPT

Replace [IP_ADDRESS] with each Pulse Stack™ monitoring server IP. Save your configuration with sudo iptables-save.

UFW (Uncomplicated Firewall) Setup

Allow Monitoring Traffic:

sudo ufw allow from [IP_ADDRESS]

Execute this command for each monitoring server IP address in our lists.

Enterprise Firewall Platforms

Cisco ASA: Create access list entries permitting traffic from monitoring IPs to your monitored services.

Palo Alto Networks: Configure security policy rules with Pulse Stack™ IP ranges as source addresses.

Fortinet FortiGate: Add address objects for monitoring IPs and create corresponding firewall policies.

Check Point: Define network objects for Pulse Stack™ servers and configure access rules accordingly.

SonicWall: Create address objects and establish firewall rules permitting monitoring traffic.

Ready to start monitoring?

Join over 2.7 million users. Free plan included, no credit card needed.

Get started free