This is a technical changelog for the Hetzner Cloud platform. To get updated about changes automatically, you can subscribe to our RSS feed
The old server plans with dedicated AMD vCPUs (CCX12, CCX22, CCX32, CCX42, CCX52, CCX62) are no longer available for order. Existing servers are not affected by this deprecation and they will continue to work. If you want to migrate an existing server to one of the new server plans with AMD vCPUs, you can use the rescale option.
These server types are not available through the API List endpoint. This also affects any usage "by name".
Applies to server types:
33)34)35)36)37)38)Our API reference documentation previously stated that the action list endpoints GET /v1/actions and
GET /v1/<resource>/actions accept the values progress, progress:asc and progress:desc for the query
parameter sort.
If used in a request, this caused the request to fail. We have removed the values for the sort parameter from our API docs.
Six new server types with dedicated AMD vCPUs are now available:
Learn more about these instances in this news article
Please note that these and new upcoming server types will use UEFI by default. If a server gets created from a snapshot, please make sure that the snapshot has an ESP / is UEFI-compatible.
Starting on 27 September 2023, the old server plans with dedicated AMD vCPUs will no longer be available for order. Existing servers are not affected by this deprecation and they will continue to work. If you want to migrate an existing server to one of the new server plans with AMD vCPUs, you can use the rescale option.
These server types will not be available through the API List endpoint after the announced date. This also affects any usage "by name".
Applies to server types:
33)34)35)36)37)38)GET /actions is deprecated. Starting 1 October 2023, it will no longer be available.
For more information about alternatives, please refer to the previous announcement "Resource Action endpoints" from 29 June 2023.
Also starting on 1 October 2023, all action endpoints will only return actions from the past 90 days.
All server plans with Intel® vCPUs (CCX11, CCX21, CCX31, CCX41, CCX51) are no longer available for order. Existing servers are not affected by this deprecation and they will continue to work. If you want to migrate an existing server with Intel® vCPUs to a server plan with AMD vCPUs, you can use the rescale option.
These server types are not available through the API List endpoint. This also affects any usage "by name".
Applies to server types:
11)12)13)14)15)We added the new endpoints /v1/<resource>/actions and /v1/<resource>/actions/{action_id} to all resources that use actions.
The new endpoints can be used instead of the global /v1/actions endpoint, to get actions of a specific product.
You can now expose routes from a Network to the vSwitch connection.
API Changes:
expose_routes_to_vswitch was added to all endpoints that return "Networks".expose_routes_to_vswitch was added to the POST /networks endpoint.expose_routes_to_vswitch was added to the PUT /networks/{id} endpoint.Starting on 18 July 2023, all server plans with Intel® vCPUs will no longer be available for order. Existing servers are not affected by this deprecation and they will continue to work. If you want to migrate an existing server with Intel® vCPUs to a server plan with AMD vCPUs, you can use the rescale option.
These server types will not be available through the API List endpoint after the announced date. This also affects any usage "by name".
Applies to server types:
11)12)13)14)15)To better communicate deprecations to API Users, we added the new response field deprecation to all endpoints that return "Server Types".
The field describes if, when, and how the resource was deprecated. If this field is set to null, the resource is not deprecated. If it has a value, it is considered deprecated.
Learn more about the field in our API docs.
This new field replaces the old deprecated field, which contained a boolean.
Please note that there will be a change regarding the id fields in our API. At the moment, the id fields are only 32 bit wide. However, this is no longer sufficient. As a result, we will use larger IDs in future. This change will not affect IDs of existing resources.
Starting on 1 September 2023, the first IDs will use 52-bit integers.
Our API had an inherent assumption that all servers, images, and ISOs used the same x86 architecture. To support the launch of our Arm64 Server Types, we added new APIs to differentiate between the architectures.
The architecture fields currently support two values: x86 and arm.
architecture was added to all endpoints that return "Server Types".Previously, the image name uniquely identified the image. This is no longer true. Instead, the image is now uniquely identified through the combination of name & architecture. This means that we now have (as an example) two images named ubuntu-22.04, one with architecture x86 and one arm. If you create servers from images (or snapshots) by passing the ID, you need to take care that you pass an image with a compatible architecture. If you create servers by passing the image name, our API will select the correct image for you.
architecture was added to all endpoints that return "Images".architecture was added to the GET /images endpoint.architecture was added to all endpoints that return "ISOs". This field can be null if the ISO is not restricted to a single architecture. We do not set the architecture for ISOs uploaded on user request.architecture was added to the GET /isos endpoint.include_architecture_wildcard was added to the GET /isos endpoint.Four new server types with Arm64 architecture are now available:
Learn more about these instances in this news article
AlmaLinux 8 and 9 are now available as images for your servers. They have the image names alma-8 & alma-9.
Three new Apps are available for your servers:
owncast)photoprism)rustdesk)The new location Hillsboro, Oregon (hil) is now available for all products. Some server types might not be available in the new location.
The datacenter hil-dc1 was also added to the API and belongs to the hil location.
The network zone us-west was also added to the API. It currently includes the hil location.
Four new Apps are available for your servers:
go)ruby)prometheus-grafana)collab-tools)When you create a cloud server, it will no longer automatically include public IP addresses (IPv4, IPv6). Instead, you can now decide for yourself which types of IPs the server should include or not. And even after creating the server, you can still change your network option by adding, removing, or swapping the server’s Primary IPs. Learn more in this news article.
All endpoints under the "Primary IPs" & "Primary IP Actions" sections were added.
GET /primary_ips was added.POST /primary_ips was added.DELETE /primary_ips/{id} was added. GET /primary_ips/{id} was added.PUT /primary_ips/{id} was added. POST /primary_ips/{id}/actions/assign was added.POST /primary_ips/{id}/actions/change_dns_ptr was added.POST /primary_ips/{id}/actions/change_protection was added.POST /primary_ips/{id}/actions/unassign was added.server.public_net.ipv4 and server.public_net.ipv6 are now nullable in all endpoints that return "Servers".public_net was added to the POST /servers endpoint.