Skip to content
IP Addresses

IP Addresses

Status200 Cloud's probes check your websites, APIs and servers from a fixed set of IP addresses. If a firewall or an allowlist sits in front of what you monitor, allow these addresses so the checks get through.

flowchart TB P["Status200 probes"] -->|"checks from the listed IPs"| F["Your firewall"] F -->|"allowed"| S["Your website, API or server"]

Where the allowlist applies

IP addresses to allow

Allow traffic from these addresses in your firewall:

  • No IP addresses configured.
Note

These addresses can change. Status200 lets you know in advance when they do. To stay up to date without watching for announcements, fetch the list when you update your firewall.

Fetch the list programmatically

The same list is served as JSON, with no API key needed, so a script can keep your firewall rules in step:

Bash
curl -s https://status200.ru/ip-whitelist
JSON
{
  "ipWhitelist": ["<list of IPs>"]
}

ipWhitelist is an array with one address per entry. To print one address per line, for example to feed into a firewall script:

Bash
curl -s https://status200.ru/ip-whitelist | jq -r '.ipWhitelist[]'

Self-hosted Status200

On your own instance, this page and the /ip-whitelist endpoint show the addresses in the instance's IP_WHITELIST setting, a comma-separated list. List the addresses your own probes send their checks from.

Kubernetes

Set the Helm chart's ipWhitelist value:

values.yamlYAML
ipWhitelist: "203.0.113.1,203.0.113.2"

Docker Compose

config.env does not pass it on to the app. Add it to the environment of the app service in a docker-compose.override.yml next to docker-compose.yml, then start Status200 again:

docker-compose.override.ymlYAML
services:
  app:
    environment:
      IP_WHITELIST: "203.0.113.1,203.0.113.2"

When nothing is set, this page shows No IP addresses configured. and the endpoint returns an empty ipWhitelist array.

Next steps