cloud-ip-ranges

StatusCake IP ranges

Current IP ranges (CIDRs) used by the StatusCake monitoring network, updated daily.

categoryUptime Monitoring
websitehttps://www.statuscake.com
ranges183 (183 IPv4, 0 IPv6)
last change
downloads685
download txt csv json — permalinks, always the latest data
curl -O https://cloud-ip-ranges.com/download/statuscake.txt

Ranges

Sample of 25 of 183 ranges. Download the full list above, or check a specific IP.

CIDR Type
13.48.110.214/32 ipv4
13.48.238.157/32 ipv4
13.49.141.132/32 ipv4
13.245.199.158/32 ipv4
13.245.222.203/32 ipv4
13.246.54.122/32 ipv4
13.247.17.60/32 ipv4
15.160.68.179/32 ipv4
15.161.88.159/32 ipv4
16.170.114.19/32 ipv4
18.102.1.62/32 ipv4
18.102.253.202/32 ipv4
34.13.166.3/32 ipv4
34.13.185.113/32 ipv4
34.13.188.75/32 ipv4
34.22.96.192/32 ipv4
34.34.97.213/32 ipv4
34.34.185.236/32 ipv4
34.40.39.31/32 ipv4
34.65.97.99/32 ipv4
34.65.97.251/32 ipv4
34.65.116.80/32 ipv4
34.65.146.108/32 ipv4
34.78.123.120/32 ipv4
34.92.43.64/32 ipv4

Blocking StatusCake

iptables

curl -sO https://cloud-ip-ranges.com/download/statuscake.txt
while read ip; do
  iptables -A INPUT -s $ip -j DROP
  iptables -A OUTPUT -d $ip -j DROP
done < statuscake.txt

ufw

curl -sO https://cloud-ip-ranges.com/download/statuscake.txt
while read ip; do
  ufw deny from $ip
  ufw deny to $ip
done < statuscake.txt

fail2ban

sudo tee /etc/fail2ban/filter.d/statuscake-block.conf << EOF
[Definition]
failregex = ^.*$
ignoreregex =
EOF

sudo tee /etc/fail2ban/jail.d/statuscake-block.conf << EOF
[statuscake-block]
enabled = true
filter = statuscake-block
action = iptables-allports[name=statuscake]
logpath = /tmp/statuscake.txt
findtime = 1
bantime = -1
maxretry = 1
EOF

curl -so /tmp/statuscake.txt https://cloud-ip-ranges.com/download/statuscake.txt
sudo systemctl restart fail2ban

pfSense / OPNsense

curl -sO https://cloud-ip-ranges.com/download/statuscake.txt
# Firewall > Aliases: new alias STATUSCAKE_BLOCK, type Network(s), import the file
# Firewall > Rules > WAN: Action=Block, Source=STATUSCAKE_BLOCK

About

These are the addresses StatusCake's uptime checks run from, updated regularly from its official list. Most people allowlist them so monitoring isn't rate-limited or blocked by a WAF; the same list also lets you identify StatusCake probes in your access logs, or block monitoring you didn't ask for. Last update was about 10 hours ago.

Other providers

AirVPN, Akamai, Alibaba, Alpha Strike Labs, Amazonbot, Amzn-SearchBot, Amzn-User, Anthropic, AppleBot, Atlassian, AWS, Azure, Backblaze, Baidu, BinaryEdge, BingBot, Bunny, CacheFly, CCBot, Censys, ChatGPT-User, ClaudeBot, Cloudflare, Datadog, DigitalOcean, DuckDuckBot, Fastly, Gabia, G-Core, GitHub, Googlebot, Google Cloud, Google Public DNS, Google Services, GPTBot, Hetzner, Hostway, Huawei Cloud, IBM Cloud, iCloud Private Relay, Internet Archive, IVPN, Leaseweb, Linode, Meta, Microsoft 365, Mistral, Mullvad, NHN Cloud, NordVPN, OpenAI ChatGPT, OpenAI SearchBot, Oracle Cloud, OVHcloud, OVPN.com, PerplexityBot, Perplexity-User, Pingdom, Private Internet Access, QUIC.cloud, Rackspace, Rapid7 Sonar, Salesforce, Scaleway, Shodan, StormWall, Stretchoid, Sucuri, Telegram, Tencent, TOR, UpCloud, UptimeRobot, Vultr, Wasabi, Windscribe, Yandex, Zoho, Zoom, Zscaler