Skip to content
LIVCK Cloud

Changelog

What changed in LIVCK Cloud — new features, improvements, fixes and announced deprecations.

2026.10.6

A new service view

Everything about a service now sits under one fixed header with tabs, and the service list can be filtered.

Improved

  • One header and tabs on every service page

    Monitoring#

    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

  • Service list with filters

    Monitoring#

    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.

  • Overview with performance by location and connections

    Monitoring#

    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.

  • Percentages in your language's format

    Console#

    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 checks from three locations

    Billing#

    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

Fixed

  • Failure reasons include your conditions

    Monitoring#

    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.