Monitoring source addresses

What this list is

• Monitoring requests from this Pinggy installation may originate from these advertised source addresses.
• Every address here was declared by an operator of this installation and explicitly published. Pinggy never derives this list from a heartbeat, from a request's source address, from a node's network interfaces, or from any address-discovery service.
• An address that is not published here is not advertised by this installation, and this page is the whole of what is advertised.

Nothing on this page is derived from a monitored endpoint, a monitoring node's telemetry, or the address any request to this server arrived from. If an address is not listed here, it is because nobody published it — not because Pinggy has not noticed it yet.

Advertised source addresses

This installation has not published any advertised source addresses. That is not a list that failed to load and it is not a claim that there are none — it means nobody has declared and published one here, so there is nothing on this page a firewall rule should be written from. Ask the operator of this installation to publish their advertised source addresses.

Basis: operator_configured · Generated at 2026-10-26 14:23:00Z · Computed as of the start of a 30-second period and cacheable for the rest of it, so a change an operator makes appears here within twice that at worst.

Using this list in a firewall

• Allow them outbound to your endpoint

  Monitoring checks are made from this installation's nodes to the endpoint you asked it to watch. Allow traffic from these addresses to the host and port of that endpoint — an HTTP or TLS check reaches the port you configured, and a TCP check reaches the port it names.

• ICMP echo replies, where an ICMP monitor is used

  An ICMP monitor sends an echo request from one of these addresses and needs the echo reply to get back. A firewall that drops ICMP will make such a monitor report the endpoint as down, whatever the endpoint is actually doing.

• Allow the whole list, not one address

  A monitor is deliberately run from several nodes, and which of them carries it changes as the fleet changes. A rule written for one of these addresses will work until placement moves, so allow every address listed here.

• Re-read this list before you troubleshoot

  The published set changes when the operator of this installation changes it. If checks that used to arrive have stopped, compare your rules against this page — or against the machine-readable contract below — before looking any further.

The same list, machine-readable

The same publication is served as JSON at /api/public/v1/source-ips, schema version 1. It carries the same addresses with the same labels, the same basis, and the same freshness, and it identifies each entry by its address — there is no internal identifier in it to key anything on.