Site24x7: IPs & Locations
Verified Site24x7 IP Addresses. Copy-Paste Firewall-Setups.
Every official Site24x7 monitoring IP: verified in real-time against the canonical source, featuring ready-to-use firewall templates. Stop false downtime alerts caused by blocked checking nodes on your infrastructure.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
Three-Step Activation & Frictionless Firewall Alignment
Bring your perimeter security rules up to date in three simple steps. Our production-ready configuration templates for common server architectures eliminate fragmented routing filters and costly check flapping.
63 IPv4 ranges from 18 published monitoring locations: one click below copies everything as a plain list or as ready-to-paste UFW, nginx, or Apache config.
Add every address to your allow list: UFW, nginx, Apache, or a Cloudflare/WAF skip rule. Partial lists cause flapping checks and false alerts.
Site24x7 updates its list occasionally. This page was verified on 2026-06-12 against the official source. Re-check after unexplained alerts or automate the sync.
Official Site24x7 Monitoring IPs
Site24x7 publishes per-location IP ranges on its official monitoring locations page.
Site24x7 (a Zoho company) checks websites from a global pool of monitoring locations and publishes the egress addresses as CIDR ranges per location. Checks rotate across locations, so partial allow lists produce location-dependent false alerts.
Whitelist the complete ranges below, or, if your monitors are pinned to specific locations, at least every location you selected (see the table further down).
This list contains 63 IPv4 ranges, verified against the official source on 2026-06-12.
IPv4 addresses 63
- 136.143.176.0/23
- 136.143.186.0/23
- 136.143.189.0/24
- 136.143.190.0/23
- 204.141.42.0/23
- 65.154.166.0/24
- 136.143.178.0/23
- 136.143.180.0/23
- 136.143.182.0/23
- 136.143.185.0/24
- 204.141.32.0/23
- 136.143.160.0/19
- 165.173.128.0/18
- 135.84.80.0/22
- 31.186.243.0/24
- 185.20.209.0/24
- 185.230.212.0/23
- 87.252.213.0/24
- 89.36.170.0/24
- 217.163.72.0/24
- 185.230.214.0/23
- 185.172.199.0/27
- 103.91.166.0/24
- 165.173.191.0/24
- 101.97.36.0/24
- 103.138.128.0/23
- 163.53.93.0/24
- 163.53.94.0/27
- 118.126.63.128/25
- 118.126.63.64/26
- 43.250.146.112/28
- 124.251.121.0/24
- 124.251.122.0/25
- 124.251.128.0/24
- 193.118.160.0/24
- 193.118.161.0/24
- 103.122.78.0/24
- 103.103.199.0/24
- 169.148.148.0/23
- 169.148.146.0/24
- 103.89.75.0/24
- 103.89.74.0/24
- 103.103.196.0/23
- 103.103.198.0/24
- 103.117.158.0/24
- 103.117.159.0/24
- 199.34.22.32/28
- 125.18.30.112/28
- 125.16.138.240/28
- 154.83.3.32/28
- 199.67.80.0/23
- 199.67.82.0/23
- 199.67.84.0/24
- 199.67.85.0/24
- 199.67.87.0/24
- 199.67.86.0/24
- 199.67.69.0/24
- 199.67.88.0/24
- 169.148.129.0/24
- 144.89.64.0/23
- 169.148.131.0/24
- 199.67.89.0/24
- 144.89.66.0/23
Last verified: 2026-06-12
Official source: https://www.site24x7.com/multi-location-web-site-monitoring.html
Where Site24x7 Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Quincy (Seattle, Washington), US | 136.143.176.0/23 · 136.143.186.0/23 · 136.143.189.0/24 · 136.143.190.0/23 · 204.141.42.0/23 · 65.154.166.0/24 |
| Dallas (Texas), US | 136.143.178.0/23 · 136.143.180.0/23 · 136.143.182.0/23 · 136.143.185.0/24 · 204.141.32.0/23 · 136.143.160.0/19 · 165.173.128.0/18 · 135.84.80.0/22 |
| Amsterdam, Netherlands | 31.186.243.0/24 · 185.20.209.0/24 · 185.230.212.0/23 |
| Dublin, Ireland | 87.252.213.0/24 · 89.36.170.0/24 · 217.163.72.0/24 · 185.230.214.0/23 · 185.172.199.0/27 |
| Melbourne, Australia | 103.91.166.0/24 · 165.173.191.0/24 |
| Sydney, Australia | 101.97.36.0/24 · 103.138.128.0/23 |
| Shanghai, China | 163.53.93.0/24 · 163.53.94.0/27 · 118.126.63.128/25 · 118.126.63.64/26 · 43.250.146.112/28 |
| Beijing, China | 124.251.121.0/24 · 124.251.122.0/25 · 124.251.128.0/24 |
| Tokyo, Japan | 193.118.160.0/24 |
| Osaka, Japan | 193.118.161.0/24 |
| Chennai, India | 103.122.78.0/24 · 103.103.199.0/24 · 169.148.148.0/23 · 169.148.146.0/24 |
| Mumbai, India | 103.89.75.0/24 · 103.89.74.0/24 · 103.103.196.0/23 · 103.103.198.0/24 · 103.117.158.0/24 · 103.117.159.0/24 · 199.34.22.32/28 · 125.18.30.112/28 · 125.16.138.240/28 · 154.83.3.32/28 · 169.148.148.0/23 |
| Riyadh, Saudi Arabia | 199.67.80.0/23 |
| Jeddah, Saudi Arabia | 199.67.82.0/23 |
| Toronto, Canada | 199.67.84.0/24 · 199.67.85.0/24 · 199.67.87.0/24 |
| Montreal, Canada | 199.67.86.0/24 · 199.67.69.0/24 |
| London, UK | 199.67.88.0/24 · 169.148.129.0/24 · 144.89.64.0/23 |
| Manchester, UK | 169.148.131.0/24 · 199.67.89.0/24 · 144.89.66.0/23 |
Whitelisting Site24x7-Monitoring IPs
Pick a format. The block below contains the complete config for every address in the list above. The plain list is also available as a .txt download.
ufw allow from 136.143.176.0/23 ufw allow from 136.143.186.0/23 ufw allow from 136.143.189.0/24 ufw allow from 136.143.190.0/23 ufw allow from 204.141.42.0/23 ufw allow from 65.154.166.0/24 ufw allow from 136.143.178.0/23 ufw allow from 136.143.180.0/23 ufw allow from 136.143.182.0/23 ufw allow from 136.143.185.0/24 ufw allow from 204.141.32.0/23 ufw allow from 136.143.160.0/19 ufw allow from 165.173.128.0/18 ufw allow from 135.84.80.0/22 ufw allow from 31.186.243.0/24 ufw allow from 185.20.209.0/24 ufw allow from 185.230.212.0/23 ufw allow from 87.252.213.0/24 ufw allow from 89.36.170.0/24 ufw allow from 217.163.72.0/24 ufw allow from 185.230.214.0/23 ufw allow from 185.172.199.0/27 ufw allow from 103.91.166.0/24 ufw allow from 165.173.191.0/24 ufw allow from 101.97.36.0/24 ufw allow from 103.138.128.0/23 ufw allow from 163.53.93.0/24 ufw allow from 163.53.94.0/27 ufw allow from 118.126.63.128/25 ufw allow from 118.126.63.64/26 ufw allow from 43.250.146.112/28 ufw allow from 124.251.121.0/24 ufw allow from 124.251.122.0/25 ufw allow from 124.251.128.0/24 ufw allow from 193.118.160.0/24 ufw allow from 193.118.161.0/24 ufw allow from 103.122.78.0/24 ufw allow from 103.103.199.0/24 ufw allow from 169.148.148.0/23 ufw allow from 169.148.146.0/24 ufw allow from 103.89.75.0/24 ufw allow from 103.89.74.0/24 ufw allow from 103.103.196.0/23 ufw allow from 103.103.198.0/24 ufw allow from 103.117.158.0/24 ufw allow from 103.117.159.0/24 ufw allow from 199.34.22.32/28 ufw allow from 125.18.30.112/28 ufw allow from 125.16.138.240/28 ufw allow from 154.83.3.32/28 ufw allow from 199.67.80.0/23 ufw allow from 199.67.82.0/23 ufw allow from 199.67.84.0/24 ufw allow from 199.67.85.0/24 ufw allow from 199.67.87.0/24 ufw allow from 199.67.86.0/24 ufw allow from 199.67.69.0/24 ufw allow from 199.67.88.0/24 ufw allow from 169.148.129.0/24 ufw allow from 144.89.64.0/23 ufw allow from 169.148.131.0/24 ufw allow from 199.67.89.0/24 ufw allow from 144.89.66.0/23
Cloudflare / WAF: create an IP Access Rule (or custom WAF skip rule) with action Allow for the addresses above, so bot fight mode and managed challenges never block probe traffic.
Whitelisting only exempts these addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly.
Frequently Asked Questions
Whitelisting everything is the safest option. If your monitors only use specific locations, the location table below lets you restrict the allow list. Remember to update it when you add locations.
The public locations page primarily documents IPv4 CIDR ranges. Check the official page for current IPv6 specifics before relying on IPv6 whitelisting.
Site24x7 adds locations and ranges over time. The official locations page is the canonical source. Re-sync it periodically or after unexplained alerts.
Both: wherever requests can be blocked. If your site sits behind a CDN or WAF (Cloudflare, AWS WAF, Akamai…), add an allow/skip rule there so probes are never challenged; if your origin firewall also filters traffic, whitelist them there too. A single missed layer is enough to cause false alerts.
Most providers expose a machine-readable source (linked above). Fetch it on a schedule, a small cron job that pulls the list and updates your firewall ruleset, instead of hardcoding addresses by hand. This page is re-verified against the official source regularly, but automation on your side is the most reliable option.
No. Allow-listing only exempts known monitoring addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly, and authentication, authorization, and TLS are unchanged. You are simply telling your firewall "these are not attackers".
A blocklist keeps known-bad addresses out; an allow/whitelist makes sure known-good addresses, here, the monitoring probes, never end up caught in a block or rate-limit rule. The two coexist: you keep blocking attackers while explicitly exempting the probes.
The IP addresses on this page belong to Site24x7 and are published by Site24x7 for whitelisting purposes. List verified on 2026-06-12 against the official source. Always cross-check with the official documentation before locking down production firewalls. All product names and trademarks are the property of their respective owners; Uptimeify is not affiliated with Site24x7. Uptimeify's own worker IPs are published at /ips.txt; a feature comparison is on our comparison page.
Monitoring Without IP Guesswork.
Protect your clients' digital assets and lock down your webserver routing. Leverage our verified network catalogs for clean whitelist setups, or migrate directly to the rock-solid, EU-only architecture of Uptimeify.