Changelog

At the registry, LIVCK reads the registration, expiry date, registrar and locks of your domains. In the zone of the extension, it checks whether the domain is listed and which name servers it points to. LIVCK neither reads nor stores data about a domain's holder.

You watch the domain behind an HTTP, SSL, TCP, DNS or ICMP check in the new Domain tab with the checkbox Watch this service's domain. It costs nothing and is ticked when the target is a domain name. A domain without a website behind it is a service of the type Domain, which counts like any other service. Domains in the navigation lists all domains of your services. Each has its own page with the registration, the name servers and their DNS provider, a checklist for its protection and the history. The API and MCP offer the same.

Alarms and notices are not active yet. Monitoring runs silently for the next few days. After that, LIVCK raises an alarm when a domain drops out of the zone or gets suspended, and sends notices about expiry, name servers, registrar, transfer lock and DNSSEC. You can already set when you hear from a domain in the Domain tab under Messages. More in the help.

When a link target lacks https://, the builder adds it as soon as you leave the field. An invalid target is named right then, not only on saving. Fields with a limit count the characters. You sort links and blocks by dragging or with the arrow keys. The preview shows the language you are writing in and follows the open block.

Ctrl+S or Cmd+S saves, Discard undoes all changes. If you leave the page with unsaved changes, the console asks first. If LIVCK refuses a save, the page jumps to the first error. With several languages, a text that applies to all languages now shows in every language tab.

With several custom links and a button, the header ran past its edge: the page name disappeared, and on smaller screens the button and the settings did too. Now whatever has no room moves into the menu behind the cog. A header that fits stays as it is.

When pausing, How long? sets when the service starts again by itself: for 30 minutes, 1 hour, 3 hours, until tomorrow or until a time of your choice, at most 90 days. Until I resume is still there. This works straight from the service list as well. The console counts down to the end. Extend and Resume now change a running pause. A note for your team is visible only in the console and never appears on a status page.

You can put an end on a manually set status, too. After that the status page shows the measured status again. If a maintenance is still running then, it shows the maintenance status instead.

If your plan has no room when the pause ends, the service stays paused. The dashboard shows it, and the owner and admins of your organization get an email. Timed pauses and statuses work through the API and MCP as well. When planning a maintenance, you can now give its end as a duration.

Incidents are split into the tabs Open, Resolved, Internal and All, each with a count. You filter by severity, service, tag, status page and time range, by whether an incident was detected automatically or reported by hand, and search the title. Entries are grouped by day. The filters are part of the address, so you can share a filtered list as a link.

Select all results resolves or deletes everything that matches the filter, across pages too, up to 500 incidents at once. When a new incident comes in, the list no longer jumps. A notice at the top shows it instead.

Maintenances are split the same way into Upcoming & running, Past, Cancelled and All, with filters for type, service, tag, status page and time range.

Every page of a service now has the same header: name, status with how long it has held, check type and target. Edit and Pause sit right next to it, Set status manually, Duplicate and Delete are in the ⋯ menu.

Below it, tabs switch between Overview, Insights, Checks and Artifacts, and for server agents between Overview, Analysis and History. When you jump to another service, you stay on the same tab.

Open services

Above the list you can filter by Status, Type, Provider and Tags. Several values in one filter show every matching service, several filters together only those that match all of them.

Below the uptime there is a strip with one field per day of the last 30 days, so the list shows when there were problems.

The overview shows the response time as a full chart and two new cards.

Performance by location shows uptime and average response time per monitoring location for the last 7 days, the slowest first. Connections shows who gets alerted during an outage, which incidents are open, which maintenances are coming up and on which status pages the service appears.

Uptime and other percentages in the console now follow the format of your language. In German that is “99,55 %”, in English it stays “99.55%”.

Solo now includes three monitoring locations instead of two. With three locations a real majority decides whether a service is down: two of three have to report the failure. If only one location reports a failure, the service counts as degraded, not as down.

Add the third location in your organization's settings or per service.

See plans

When a check failed because one of your conditions matched, Insights showed “No failures” under Failure reasons. Those checks now appear there as a cause of their own.

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.