Changelog

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.

Through the Model Context Protocol (MCP), your AI assistant works with LIVCK directly. You write, for example, “Schedule maintenance tonight from 2 to 4 am for every service tagged db and announce it”. The assistant prepares the maintenance and shows you the text, times and recipients.

It opens incidents and writes their updates, schedules maintenance, creates or edits services and looks for the cause of an outage. Depending on the connection's rights and scope, status pages, on-call, SLA, activity and support tickets come on top.

You create the connection under AI & MCP in your organization's settings. For 30 clients, among them Claude Code, Cursor, VS Code, OpenAI Codex, Gemini CLI, OpenCode and Claude Desktop, the console shows you the finished configuration. Reading is included on every plan, the free one too. Writing comes with Solo and up.

Connect an AI assistant

Anything that reaches customers, wakes someone up, silences alerting or deletes something is shown as a preview first: recipients, texts per language, times and what will be lost. It only runs once you confirm. If someone on your team changes the text after your preview, LIVCK does nothing and the assistant has to ask you again.

For clients that do not ask on their own, choose Approve with a click in the browser. The action then waits under Approvals until you approve it.

Each connection gets No access, Read, Write or Delete per area. Three switches decide what reaches the outside: Notify customers, Wake on-call and Silence or change alerting. A connection never has more rights than the person who created it. Its token only works for MCP, not for the API.

New entries in Activity now show how a change was made: in the browser on a desktop or phone, through the API with the token's name, or by an AI assistant with its client's logo, for example “via Claude Code”. With the Channel filter you can show only the changes made by AI assistants.

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.

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.

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.