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.

Put your badge together, copy the snippet and paste it into your website. The badge shows the current status and leads to your status page with one click. Free for every public status page.

Open the badge generator

The overview of every status page shows its badge. Customise badge opens the generator.

An internal incident is on no status page, and nobody is notified. A notice at the top of the incident now says so. In the incident list, on the dashboard and on the service page it carries the Internal badge, and the list can be filtered by it.

When creating an incident, Publish now decides whether it appears right away or stays internal for now. Publish puts it on your status pages later. Before that you see where it appears and which message goes to how many subscribers. Whether it goes out at all is your call, through the API and MCP as well. Make internal takes it off every status page at once.

If you mark an incident as resolved only later, enter under Resolved at when it was really over. This works when resolving, in the update form and on the edit page. The downtime of the affected services follows it. AI assistants can set the time through MCP as well.

In Activity you can now pick several people, categories and channels at once. The active filters sit above the list and can be removed one by one. To covers the whole day in your time zone.

An update with the status Resolved closes the incident. In the update form it therefore now needs the Resolve Incidents right, as it already did in the API. Notes on an incident that is already resolved still work without it.

When you make an internal incident public, your subscribers now get the latest message. Until now they got the first one, so for an incident that was already resolved it still said “We are investigating …”. If you publish an incident again, a message that was already sent no longer goes out a second time unless you ask for it.

Visitors now see your status page in their browser's language. If the page does not offer that language, it appears in English if available, otherwise in its default language. Until now, English-speaking visitors to German-only status pages sometimes landed on an English version that does not exist.

Your status page now follows the setting on each visitor's device. If a phone or computer is set to dark, the status page appears dark too. When the device changes its setting, the open page changes with it. This applies to all status pages from now on. There is nothing to set up.

Through the gear icon on the status page, visitors pick Light, Dark or System themselves. The browser remembers the choice. With System, the page follows the device again.

In the Branding tab you set System, Light or Dark for each status page. With Visitors can switch turned off, everyone sees exactly that appearance and the switch on the status page is hidden.

Open status pages

Status pages have two new fields in the API: appearance (system, light or dark) and allow_appearance_switch. You set both with PATCH /v1/statuspages/{id}.

Your primary colour now takes effect on the status page and stays readable in light and dark mode. Where the contrast with the background falls short, we adjust its brightness.

Every status page now has a preview image of its own. It shows your page's name, logo and primary colour. At the bottom is the address from the shared link, followed by the current status. If someone shares a link on your own domain, the image shows that domain too. While everything runs, the image glows in your primary colour, otherwise in the colour of the status.

Every incident and every maintenance gets an image of its own with title, time and affected components. There is nothing to set up.

On the Free plan the image carries a small LIVCK logo at the bottom right, just like the footer of your status page.

In the SEO tab of your status page's settings you decide what search engines and link previews show:

• title, description and the subtitle in the image, per language of your status page
• background of the image: automatic, light or dark
• whether previews show the current status
• whether incidents and maintenance get images of their own
• whether search engines may list the page

The tab shows the image as it appears when shared. Platforms often keep previews for hours, messengers keep them in old messages for good. If a shared link should never show an outdated status, turn off the status in previews.

Status pages now have a seo field in the API with the same settings as the tab. With PATCH /v1/statuspages/{id}, seo replaces all of them at once. Whatever you leave out goes back to its default, and "seo": {} resets everything. If you leave out seo entirely, everything stays as it is.

Your organisation's settings now have a time zone. The preview images of incidents and maintenance give start and end in it. The default is Europe/Berlin.

Status pages with a password or an email whitelist no longer appear in search engines. Their preview images show only name, logo and address, never a status. Search engines also no longer pick up the links subscribers use to confirm or manage their subscription.

The time zone picker now groups zones by continent, with Europe at the top and cities in alphabetical order. This applies wherever you pick a time zone: in the organisation, for heartbeats and for SLA objectives.

Saving a status page reset the logo size to Medium. It now stays as you set it. The form also uploaded a newly chosen logo again on every further save. That is fixed too.

On roadmap.livck.cloud you can see what we are working on right now, what comes next and what is done. With your LIVCK account you can:

• vote on topics
• follow topics
• join the discussion
• submit ideas of your own

A submission is first seen only by you, your organisation and us. If it appears on the board, it does so in our wording and without your name.

Our Discord bot brings your status page into a Discord channel. Until now that worked only with Self-Hosted; since 22 September it also works with status pages from LIVCK Cloud. To set it up:

1. Invite the bot to your Discord server.
2. Run /livck subscribe in the channel you want and paste the address of your status page. Cloud or Self-Hosted, the bot works that out itself.

Incidents and maintenance then appear as threads of their own.

Three new endpoints return everything around a service:

• GET /v1/services/{id}/incidents: its incidents
• GET /v1/services/{id}/maintenances: its maintenance
• GET /v1/services/{id}/checks: its check results with location, status, HTTP code, error and timings

That way the API also tells you why a service was unreachable. /v1/incidents and /v1/maintenances can also be narrowed to several services with service_ids.

Write requests (POST) accept an optional Idempotency-Key header. If the response to a successful request never arrives, for example because of a timeout, just repeat it with the same key. You get the original response back, and nothing is created twice. The only exception is uploading logos and favicons.

• GET /v1/tags now filters by label and key.
• POST /v1/tags/ensure creates a tag or returns the existing one.

No more paging through a list to find a tag.

If part of creating a service through the API fails, such as setting its tags, no half-created service is left behind any more. A second attempt therefore creates no duplicate.

Services and status pages can be bundled into an area and granted to specific teams or roles. Every other member sees nothing of them — not in lists, not in incidents, not in notifications.

With no areas, nothing changes: everything stays visible to everyone, as before.

Open access areas

LIVI shows the overall state of every service. Colour and face change as soon as something goes down.

After the pilot it is open to every organisation: CPU, memory, disks and running services next to your other checks. Nobody has to request access any more.

Connect a server

The server overview now shows every partition, not just the fullest.

A ready-made set for the status page, instead of adding each series by hand.