# July 2026 (/docs/news/2026/news-07-26)



<NewsSection tags={['platform', 'ebm', 'managed_kubernetes']}>
  ### 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](https://developers.servers.com/api-documentation/v1/#tag/Dedicated-Server/operation/ListNetworksForADedicatedServer)

  <Badge type="improved" />

  <Tag>
    Platform
  </Tag>

  <Tag>
    Enterprise Bare Metal
  </Tag>

  <Tag>
    Managed Kubernetes
  </Tag>
</NewsSection>

<NewsSection tags={['managed_kubernetes']}>
  ### 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.

  <Badge type="improved" />

  <Tag>
    Managed Kubernetes
  </Tag>
</NewsSection>

<NewsSection tags={['managed_kubernetes']}>
  ### 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](https://www.servers.com/docs/managed-kubernetes/getting-started/)

  <Badge type="new" />

  <Tag>
    Managed Kubernetes
  </Tag>
</NewsSection>

<NewsSection tags={['billing', 'account']}>
  ### 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

  <Badge type="improved" />

  <Tag>
    Billing
  </Tag>

  <Tag>
    Account
  </Tag>
</NewsSection>

<NewsSection tags={['account']}>
  ### 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](https://www.servers.com/docs/account/concepts/#subscription)

  <Badge type="new" />

  <Tag>
    Account
  </Tag>
</NewsSection>

<NewsSection tags={['scalable_bare_metal', 'account']}>
  ### 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.

  <Badge type="new" />

  <Tag>
    Scalable Bare Metal
  </Tag>

  <Tag>
    Account
  </Tag>
</NewsSection>

<NewsSection tags={['platform', 'ebm', 'l2_segments']}>
  ### 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](https://developers.servers.com/api-documentation/v1/#tag/Dedicated-Server)

  [L2 Segment API reference](https://developers.servers.com/api-documentation/v1/#tag/L2-Segment)

  <Badge type="new" />

  <Tag>
    Platform
  </Tag>

  <Tag>
    Enterprise Bare Metal
  </Tag>

  <Tag>
    L2 Segments
  </Tag>
</NewsSection>

<NewsSection tags={['l2_segments']}>
  ### 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.

  <Badge type="fixed" />

  <Tag>
    L2 Segments
  </Tag>
</NewsSection>

<NewsSection tags={['account']}>
  ### 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.

  <Badge type="fixed" />

  <Tag>
    Account
  </Tag>
</NewsSection>

<NewsSection tags={['scalable_bare_metal']}>
  ### 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.

  <Badge type="fixed" />

  <Tag>
    Scalable Bare Metal
  </Tag>
</NewsSection>