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.
. 103.21.244.0/22
. 103.22.200.0/22
. 103.31.4.0/22
. 104.16.0.0/13
. 104.24.0.0/14
. 108.162.192.0/18
. 131.0.72.0/22
. 141.101.64.0/18
. 162.158.0.0/15
. 172.64.0.0/13
. 173.245.48.0/20
. 188.114.96.0/20
. 190.93.240.0/20
. 197.234.240.0/22
. 198.41.128.0/17
IPv6. 103.21.244.0/22
. 103.22.200.0/22
. 103.31.4.0/22
. 104.16.0.0/13
. 104.24.0.0/14
. 108.162.192.0/18
. 131.0.72.0/22
. 141.101.64.0/18
. 162.158.0.0/15
. 172.64.0.0/13
. 173.245.48.0/20
. 188.114.96.0/20
. 190.93.240.0/20
. 197.234.240.0/22
. 198.41.128.0/17
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 192.168.1.1 -j ACCEPT sudo iptables -A INPUT -s 192.168.2.1 -j ACCEPT sudo iptables -A INPUT -s 192.168.3.1 -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 192.168.1.1 sudo ufw allow from 192.168.2.1 sudo ufw allow from 192.168.3.1
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 192.168.1.1 access-list Webstatus247-ACL extended permit ip any 192.168.2.1 access-list Webstatus247-ACL extended permit ip any 192.168.3.1
Step 2
Apply the ACL to the interface: access-group Webstatus247-ACL in interface outside
Step 3
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.
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.