Changelog
What changed in LIVCK Cloud — new features, improvements, fixes and announced deprecations.
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.