Skip to content
LIVCK Cloud
Transparency

The LIVCK bot

See “LIVCK” in your server logs? Here's who we are, why we're knocking on your door – and how to control the access.

User-Agent: LIVCK-StatusSync/1.0 (+https://livck.cloud/bot)

Who's visiting

LIVCK Cloud is a German uptime-monitoring and status-page platform, hosted at Hetzner and GDPR-compliant. Our bots fetch websites and public status pages – read-only, with a clear user agent, and respecting timeouts and size limits.

  • Read-only GET requests – we change nothing.
  • Every request identifies itself via user agent and links to this page.
  • Operated from Germany, GDPR-compliant.

Our user agents

Three bots, three clearly separated purposes – so your logs tell you at a glance what's going on.

Availability checks

Read-only
LIVCK-Worker/1.0

Checks whether a service is reachable – HTTP, TCP, DNS, ICMP or SSL.

Why you see this
Someone monitors this service with LIVCK.
Frequency
Regularly, at the configured check interval (from 30s).

Status-page mirroring

Read-only
LIVCK-StatusSync/1.0

Reads your public status page to mirror the state it reports.

Why you see this
A LIVCK customer depends on your service and mirrors your status page.
Frequency
At most every 60s; multiple components are coalesced into one request.

Favicon fetch

Read-only
LIVCK-FaviconBot/1.0

Fetches a monitored host's favicon once, for display.

Why you see this
A monitored host is shown with its icon in the LIVCK interface.
Frequency
Rarely – only when needed, then cached.

Is this really LIVCK?

Genuine LIVCK requests carry one of the user agents above with the suffix “+https://livck.cloud/bot” and come from our fixed monitoring probes. You can fetch their current egress IPs anytime – as plain text or JSON – and add them to your firewall allowlist.

Fetch the egress IPs
app.livck.cloud/ips
Defaulttext/plain

One IP per line – ideal for firewall rules.

curl https://app.livck.cloud/ips
203.0.113.10
203.0.113.11
2001:db8::a
JSONapplication/json

Structured: ipv4, ipv6 and generated_at.

curl -H "Accept: application/json" \
     https://app.livck.cloud/ips
{
  "ipv4": ["203.0.113.10", "…"],
  "ipv6": ["2001:db8::a", "…"],
  "generated_at": "…"
}

Or without a header: ?format=json

Availability checks are actively set up by the respective LIVCK customer and therefore do not consult robots.txt. Status-page and favicon fetches are made considerately: timeouts, a size limit and low frequency.

How to control access

Block

Don't want to be fetched? Block the user agent or our IP ranges. For availability checks, the customer who set it up will then see the service as unreachable.

Frequency

The fetch frequency is limited by design – status-page fetches at most every 60s and coalesced, favicons only rarely, checks at the interval the customer chose. If it's still too much, reach out and we'll throttle or pause specifically.

Contact & abuse

Send questions, complaints or opt-out requests to our team – we respond promptly.

How our bots behave

Read-only GET requests only – no forms, no writes.
A unique user agent linking to this page.
Hard timeouts and a 1 MB response limit.
No JavaScript, no rendering – just the raw response.
No login areas, no bypassing of access controls.
Multiple components of one source are coalesced into a single request.

More questions about our bots?

Get in touch – we help with allowlists, IP ranges or opt-outs.

Contact us