Changelog

Next to the grace period a heartbeat now has Confirmations before alerting (1 to 5). At 1 we alert immediately on the first missed interval, exactly as before.

The default is 2 for intervals up to five minutes and 1 above that. The reason: confirmations times interval is your time to alert — on a daily backup two rounds would be two days.

Two cases still alert immediately, whatever you set: a ping to /fail, and a run that started but never reported finishing. Your script reports both itself, so nothing was lost in transit.

We have already set existing heartbeats with a short interval to 2. Their time to alert grows by one interval — if you do not want that, set the value to 1.

Open heartbeats

Until now a single missing ping was enough to flip a heartbeat to Down and notify you. On a job that runs every minute that meant: one request lost in transit becomes an incident — even though your job ran fine.

Now we count. Only when several intervals are missing in a row do we treat the service as down. Every incoming ping resets the counter: one hiccup in the morning and one in the afternoon do not add up.

Recovery stays immediate — the first ping that arrives again puts the service back to Up.

In the service overview, every target shows the logo of its provider, such as Hetzner, Cloudflare or STACKIT. For server agents it appears next to every IP address. The tooltip shows the name, country, addresses and whether a CDN sits in front.

We detect new and changed services within a few seconds.

Open services

Checks from Northern Europe now run via Helsinki. The location sits on its own network (AS202053), so it counts as a full independent vote when several locations decide whether a service is really down. Like every location it is optional: you decide in your settings whether Helsinki should check your services — until then it receives no checks from you.

UpCloud Oy (Helsinki, Finland) runs the new checking location and is now listed in our public provider list and in Annex 2 of the data processing agreement. The location is inside the EU, so no standard contractual clauses are needed. We clarified two things in the DPA: checking locations only receive your data once you select them — and we described what the checking servers actually do: results are sent to us encrypted straight away, and if that fails for a moment they sit locally on the server until the transfer goes through.

Checks from the US East Coast now run from New York. Ashburn was the original plan; New York took its place because it sits on its own network and therefore judges independently of our German locations. You can select it in your service settings.

Both channels are now in our public provider list and in the data processing agreement. Nothing about the channels themselves changes: data is only sent once someone has added and confirmed the contact method.

Add a provider's status page and pick the services you depend on. They then sit in your list like any other service, ready for your status page.

Atlassian Statuspage, Cachet and LIVCK-hosted pages are supported, with ready-made connections for well-known providers.

Open sync sources

Mirrored services can be renamed. LIVCK tags the provider and the connection automatically.

Mirrored services show their provider's icon.

Add, remove or rename services without recreating the connection.

Their status comes from the provider — our probes never query them directly.