What's new on Servers.com

July 2026

Public API — network objects include first_ip and gateway

Networking can now be configured on EBM, SBM, and Kubernetes bare metal nodes without manually computing addresses.

• first_ip and gateway added to the network object returned by the EBM, SBM server, and Kubernetes bare metal node network endpoints
• gateway is null for routed networks and for /32 (IPv4) or /128 (IPv6) networks

Networks API reference

Kubernetes worker nodes — add/remove blocked below version 1.27

Worker nodes can no longer be added to or removed from clusters running Kubernetes versions earlier than 1.27. The Add node and Remove nodes controls are disabled for these clusters in the Customer Portal.

Managed Kubernetes — clusters can be created without worker nodes

A Kubernetes cluster can now be created without any worker nodes and isn't billed until worker nodes are added.

The cluster becomes Active as soon as the control plane is ready, allowing worker nodes to be added later.

Managed Kubernetes — Getting started

Billing and Identity & Access navigation — restructured

Finding invoices, statements, and access-control settings now takes fewer clicks and uses clearer labels.

• Invoice Groups moved under Invoices as a separate tab
• Top Up Balance is now available as a button on the Payment Methods page
• Account Statements, Payment Details, Identity and Access, and Management renamed to Statements, Payment Methods, Identity & Access, and Access Control respectively

Subscriptions — new Type and Status fields

Subscription records now show more clearly how each address relates to an account, reducing the risk of notifications going to the wrong place.

• Subscriptions now have a Type: Direct (exact email match with an account member) or Additional (linked to the account, email can differ)
• a Direct subscription is created automatically when a new member is invited, with the subscription role chosen at invitation time
• a Direct subscription is removed automatically if the member is revoked from the account, and cannot be deleted manually
• a subscription's secondary email is now a separate Additional subscription instead of a field on the same record
• the Email field can no longer be edited after a subscription is created

Note: subscription status will support a confirmation/unsubscribe flow in a future update.

Account concepts — Subscription

Scalable Bare Metal — now covered by IAM

SBM resources can now be restricted per team and role, instead of being visible and manageable by every account member.

Granular IAM permissions now gate SBM ordering, server actions (power, reinstall, cancel, VNC), and resource-group assignment on the Portal.

Public API — rack unit and L2 segment membership added to EBM servers

EBM server details now include rack placement and L2 segment membership without additional lookups.

• rack unit data is now included for hosts placed in a customer's private rack
• GET /v1/hosts/dedicated_servers/{id}/l2_segments — new endpoint returning the L2 segments a host is a member of, or an empty array if none

Dedicated Server API reference

L2 Segment API reference

L2 Segments page — errors resolved for segments with many members

Opening the L2 Segments page and managing members no longer fails intermittently for segments with a large number of members.

Server errors that occurred on the L2 Segments page for large segments have been resolved.

Request creation — Cloud Server instances selectable with CloudServersRead

Users with only CloudServersRead permission can now select a Cloud Server instance in the Choose server block when creating a request.

SBM order emails — iDRAC credentials no longer included

Scalable Bare Metal order-completion emails no longer include iDRAC credentials, which were never intended to be provided for SBM.

The CSV attachment sent after an SBM order completes no longer contains OOB IP, login, or password columns; Enterprise Bare Metal order emails are unaffected.

June 2026

Managed Kubernetes — controlled version lifecycle introduced

Managed Kubernetes clusters now follow a support lifecycle for Kubernetes versions, keeping clusters on supported and secure versions.

• each Kubernetes version now has three lifecycle dates: maintenance start, end-of-life (EOL), and automatic upgrade
• notifications appear in the portal and by email as a cluster approaches each date
• when a cluster reaches its automatic upgrade date and a safe upgrade path exists, the cluster is upgraded to a supported version, using the configured maintenance window where possible

Current version status and upgrade dates are shown in the Managed Kubernetes section of the portal.

Note: a cluster that fails auto-upgrade three times is flagged for unmanaged conversion, which starts the offboarding notice sequence.

More in version support policy

Managed Kubernetes — DNS-based high availability API

Cluster API access can now stay reachable through DNS endpoints instead of a single IP, reducing disruption during failover.

• Portal, and kubeconfig generation support public and private DNS endpoints in the form public.<zone>:6443 / private.<zone>:6443
• enabled by default for new clusters
• existing IP-based kubeconfigs remain fully compatible

Resource groups — aggregative type added for L2 Segments

L2 Segments can now be organized and access-controlled through IAM the same way other resources are.

• a resource group type — Aggregative or Resource-based — must be chosen on creation
• a default aggregative resource group is created automatically and existing L2 Segments assigned to it
• L2 Segment pages now respect IAM permissions for Hosts, Kubernetes nodes, and Direct Connect

L7 Load Balancer — GRPC and HTTP/2 combination restricted

New load balancers can no longer be created with a protocol combination known to cause issues.

• creating or editing an L7 load balancer is now blocked when GRPC/GRPCs protocols are combined with HTTP/2 enabled

Note: existing load balancers already using this combination are unaffected and continue to work.

AI Compute — access request form enabled

Customers interested in AI Compute can now request access directly from the Customer Portal instead of contacting sales separately.

Dedicated servers — OS reinstall via Terraform

Dedicated server reinstalls can now be scripted as part of infrastructure-as-code workflows.

Reinstalling the operating system on dedicated servers is now supported through the Terraform provider.

May 2026

GPG key management — governed by IAM permissions

Access to GPG key creation and deletion in the Portal is now controlled by IAM permissions, consistent with other key management operations.

April 2026

IAM permission policies — export and import across accounts

Permission policies can be exported to JSON and imported into other accounts, making it easier to maintain consistent access configurations across a multi-account organisation. More in IAM documentation.

SSL certificate renewal errors — actionable messages returned

An issue that caused SSL certificate renewal failures to return unclear error responses has been resolved; the API now returns specific, actionable messages.

Remote Block Storage — available in beta

Scalable block storage can be added to servers without replacing or installing local disks. More in Remote Block Storage.

• create, attach, resize, disable, and delete volumes via Customer Portal, Public API, Terraform, and Kubernetes (RBS CSI driver)
• currently available in AMS7; volumes can be used from other locations, but IOPS and bandwidth depend on network latency
• volumes can be resized and temporarily disabled without deletion

Note: this is a beta release. For best performance, use RBS with servers in the same datacenter (AMS7).

Managed Kubernetes — pod limit increased to 250 per node

New clusters support up to 250 pods per worker node, up from 110. The Pod CIDR per node has been widened to /23 to accommodate the higher pod count.

Note: applies to new clusters only. Existing clusters and nodes added to existing clusters are unaffected. No action required.

iPXE boot — available for EBM servers

EBM servers can boot from a custom iPXE script over the network on every start, without going through the standard OS installer. More in Public API.

• two modes available: public iPXE boot (via public network interface) and private iPXE boot (via private interface)
• script URL and optional user_data string configurable without reprovisioning
• MAC addresses and DNS server addresses automatically injected as variables before the script runs
• activate at order time via the features field, or on an existing server via /features/public_ipxe_boot/activate or /features/private_ipxe_boot/activate
• to update the script on a running server: deactivate, update ipxe_config via PUT, reactivate, and reboot

March 2026

IAM — beta release with updated Team and Permission Policy management

Identity and Access Management is now in beta, with documentation and UX improvements that make it easier to configure access control for account members and resource groups. More in IAM documentation.

Kubernetes Node Groups — available

Worker nodes can be grouped within a cluster to separate workloads logically and apply consistent scheduling labels across a group. More in Node Groups.

• create, rename, and delete node groups from the Portal or via /v1/kubernetes_node_groups PAPI endpoint
• nodes can be assigned to a group at add time, or moved later individually or in bulk
• existing clusters have been automatically included into a default node group

Kubernetes worker nodes — addable in nearby locations

When the cluster's primary location has no available bare-metal capacity, worker nodes can be added in a nearby location with the same location prefix (e.g. AMS2 or AMS3 for a cluster in AMS1). More in Add a worker node.

• cross-location connectivity handled automatically over GPN; no manual network configuration required
• Portal shows a Location selector when adding a node and a Location column in the nodes list