Changelog
What changed in LIVCK Cloud — new features, improvements, fixes and announced deprecations.
2026.09.3
Link previews for status pages
When someone shares the link to your status page in Slack, Teams, WhatsApp or LinkedIn, a preview image now appears with your logo, your address and the current status. Incidents and maintenance get images of their own. In the new SEO tab you decide what previews and search engines show.
New
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
seofield in the API with the same settings as the tab. WithPATCH /v1/statuspages/{id},seoreplaces all of them at once. Whatever you leave out goes back to its default, and"seo": {}resets everything. If you leave outseoentirely, 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.
Improved
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.
Fixed
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.
2026.08.3
New checking location: Helsinki
A ninth location is now checking your services — Helsinki, our first in Northern Europe.
New
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.
Improved
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.
2026.08.2
New checking location: New York
The US location has arrived, in a different city than originally planned. We have also updated our list of service providers.
New
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.
Improved
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.
2026.07.4
Access areas
Larger organisations can now decide which services and status pages each team gets to see.
New
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.
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.