Our measurement traffic — and what you can do about it
Seeing recurring requests from us and want them to stop? The fastest route does not involve us at all.
Just block us
Our probes have fixed addresses and we publish them. Put them in your firewall — effective immediately, no ticket, no waiting. That is what the list is for.
As a plain list
curl https://app.livck.cloud/ips
As JSON
curl https://app.livck.cloud/ips?format=json
What happens then: whoever uses LIVCK to monitor your service will see it as unreachable from that location. That is not a bug, it is exactly the measurement. Whether it becomes an incident is decided by a majority across the networks involved — from three independent networks upwards, a single blocked location no longer carries one.
How to recognise us
Two ways, depending on the check type — and one of them is the only one that exists for TCP, ICMP, DNS and TLS.
For web requests
LIVCK-Worker/1.0 (+https://livck.cloud/bot)HTTP and HTTPS checks identify themselves in the user agent and link to our bot page.
For everything else
app.livck.cloud/ipsTCP, ICMP, DNS and TLS carry no user agent. There the source address is the identification: if it is on our published list, it is us — otherwise it is not.
For those check types the list above is the only reliable answer. It changes when we add or retire locations, so query it rather than copying addresses down.
If you would rather write to us
For anything blocking cannot solve — legal concerns, misbehaving systems, security reports.
- To route it quickly we need:
- the source IP concerned
- timestamp and time zone
- an excerpt from your log
We reply within three working days.