Find Your Nearest WebStatus247 Location

Expanding Our Reach to Serve You Better

The key to smooth monitoring with WebStatus247 is allowing the right traffic through your firewall. This page provides a step-by-step guide to whitelisting WebStatus247 IP addresses across popular firewalls so your checks run without interruption. Use the lists below to adapt rules to your environment.

Strategic Importance of Our Global Locations

Our global footprint is about more than data centers—it’s how we deliver performance, meet local compliance/data sovereignty, and scale to the needs of different markets.

Each site helps us serve diverse requirements while maintaining consistent, cross-region reliability and support.

IPv4
. 207.58.175.222/32
. 142.91.102.154/32
. 147.93.159.58/32
. 5.104.83.79/32
. 142.91.106.215/32
. 185.218.126.119/32
. 85.17.179.239/32
. 149.102.128.152/32
. 23.81.34.107/32
. 85.239.232.254/32
. 23.19.230.155/32
. 209.126.11.145/32
. 154.53.44.210/32
. 131.153.218.195/32
. 31.97.99.165/32
. 209.50.227.73/32
. 139.84.232.255/32
. 170.64.141.237/32
. 154.26.158.130/32
. 78.142.242.78/32
. 212.85.15.209/32

Firewall Configuration Guides

Use these steps for common firewalls to allow monitoring traffic.

  • Windows Defender Firewall

    1. Open Control Panel → System and Security → Windows Defender Firewall.

    2. Click Advanced settings.

    3. Inbound Rules → New Rule…

    4. Choose Custom Rule → Next.

    5. Specify WebStatus247 source IPs and required ports (e.g., 80, 443).

    6. Save. Repeat similar steps for Outbound Rules if needed.

    For details, see Microsoft’s documentation.

  • Linux iptables

    Open a terminal and run the following to allow WebStatus247 IPs:

      sudo iptables -A INPUT -s 207.58.175.222/32 -j ACCEPT
sudo iptables -A INPUT -s 142.91.102.154/32 -j ACCEPT
sudo iptables -A INPUT -s 147.93.159.58/32 -j ACCEPT
sudo iptables -A INPUT -s 5.104.83.79/32 -j ACCEPT
sudo iptables -A INPUT -s 142.91.106.215/32 -j ACCEPT
sudo iptables -A INPUT -s 185.218.126.119/32 -j ACCEPT
sudo iptables -A INPUT -s 85.17.179.239/32 -j ACCEPT
sudo iptables -A INPUT -s 149.102.128.152/32 -j ACCEPT
sudo iptables -A INPUT -s 23.81.34.107/32 -j ACCEPT
sudo iptables -A INPUT -s 85.239.232.254/32 -j ACCEPT
sudo iptables -A INPUT -s 23.19.230.155/32 -j ACCEPT
sudo iptables -A INPUT -s 209.126.11.145/32 -j ACCEPT
sudo iptables -A INPUT -s 154.53.44.210/32 -j ACCEPT
sudo iptables -A INPUT -s 131.153.218.195/32 -j ACCEPT
sudo iptables -A INPUT -s 31.97.99.165/32 -j ACCEPT
sudo iptables -A INPUT -s 209.50.227.73/32 -j ACCEPT
sudo iptables -A INPUT -s 139.84.232.255/32 -j ACCEPT
sudo iptables -A INPUT -s 170.64.141.237/32 -j ACCEPT
sudo iptables -A INPUT -s 154.26.158.130/32 -j ACCEPT
sudo iptables -A INPUT -s 78.142.242.78/32 -j ACCEPT
sudo iptables -A INPUT -s 212.85.15.209/32 -j ACCEPT

    Step 2

    Save changes: sudo iptables-save

    Step 3

    Official guide: iptables documentation

  • Linux UFW (Uncomplicated Firewall)

    Open a terminal.

    • Run the following commands:

      • sudo ufw allow from 207.58.175.222/32
sudo ufw allow from 142.91.102.154/32
sudo ufw allow from 147.93.159.58/32
sudo ufw allow from 5.104.83.79/32
sudo ufw allow from 142.91.106.215/32
sudo ufw allow from 185.218.126.119/32
sudo ufw allow from 85.17.179.239/32
sudo ufw allow from 149.102.128.152/32
sudo ufw allow from 23.81.34.107/32
sudo ufw allow from 85.239.232.254/32
sudo ufw allow from 23.19.230.155/32
sudo ufw allow from 209.126.11.145/32
sudo ufw allow from 154.53.44.210/32
sudo ufw allow from 131.153.218.195/32
sudo ufw allow from 31.97.99.165/32
sudo ufw allow from 209.50.227.73/32
sudo ufw allow from 139.84.232.255/32
sudo ufw allow from 170.64.141.237/32
sudo ufw allow from 154.26.158.130/32
sudo ufw allow from 78.142.242.78/32
sudo ufw allow from 212.85.15.209/32

    Step 2

    Confirm changes: sudo ufw status

    Step 3

    More details: Ubuntu UFW documentation

  • Cisco ASA Firewall

    Access the ASA via ASDM or CLI and add access-list entries:

      access-list Webstatus247-ACL extended permit ip any 207.58.175.222 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 142.91.102.154 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 147.93.159.58 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 5.104.83.79 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 142.91.106.215 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 185.218.126.119 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 85.17.179.239 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 149.102.128.152 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 23.81.34.107 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 85.239.232.254 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 23.19.230.155 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 209.126.11.145 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 154.53.44.210 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 131.153.218.195 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 31.97.99.165 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 209.50.227.73 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 139.84.232.255 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 170.64.141.237 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 154.26.158.130 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 78.142.242.78 0.0.0.0
access-list Webstatus247-ACL extended permit ip any 212.85.15.209 0.0.0.0

    Step 2

    Apply the ACL to the interface: access-group Webstatus247-ACL in interface outside

    Step 3

    See Cisco ASA documentation.

  • Palo Alto Networks Firewall

    Log in to the admin console → Policies → Security.

    Add a rule with WebStatus247 IPs and allow required services (HTTPS, ICMP).

    For detailed steps, visit Palo Alto documentation.

  • Fortinet FortiGate Firewall

    Log in → Policy & Objects → Firewall Policy.

    Create a policy allowing WebStatus247 IPs. Ensure action is Allow.

    Official guide: Fortinet documentation.

  • Check Point Firewall

    Open SmartConsole → Security Policies → Access Control Policy.

    Add a rule allowing WebStatus247 IPs. Save and install the policy.

    See Check Point documentation.

  • SonicWall Firewall

    Log in → Firewall → Access Rules. Add a rule allowing WebStatus247 IPs.

    For step-by-step instructions, visit SonicWall documentation.

Have any questions? Get in Touch

Best Practices for Firewall Configurations

Backup configurations: Before changes, export or snapshot your current settings.

Test connectivity: Verify WebStatus247 can reach your endpoints after changes.

Update regularly: Keep firewall firmware and definitions current.

Need Help?

If you run into issues, contact our support team or your vendor’s official docs. Following these steps helps WebStatus247 monitor your services smoothly and provide accurate, real-time insights.

Location: Offices, Address & Contact Info