> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/changelog.md). # Changelog Product updates across all i3D.net services. Newest entries first. Tags indicate which product an update applies to. An entry can carry multiple tags. > **RSS / notifications:** Coming soon. *** ## 2026-10-21 — Dedicated Networks API: choose your own private subnet `Dedicated Networks` You can choose the exact subnet of a private network when you create it, from the private IP ranges. The network becomes `active` with that subnet, so you can follow the same IP addresses in i3D.net systems that you use in your own address plan. IPv4 and IPv6 are both supported. See [Choosing the private subnet yourself](/connectivity/dedicated-networks-api/creating-a-network.md#choosing-the-private-subnet-yourself). **How to set it up** 1. Make sure you have write access. 2. In your create-network request, set `addressing.prefixes` to `[{"cidr": "10.20.30.0/24"}]` instead of `family` and `size`. 3. Wait until the network is `active`. If the subnet is already in use on one of your private networks, the network ends in state `failed`. Create it again with another subnet and a new UUID. You can still let i3D.net generate the subnet: send `family` and `size` as before. *** ## 2026-10-16 — Detailed DDoS attack reports `Anti-DDoS` `GLAD Advanced` `GLAD Premium` You can receive a detailed DDoS report for each attack that targets your server or IP address. It arrives alongside the standard attack report and shows the signature of the attack: the top five destination ports and the top five protocol and packet-size combinations, ranked by average packets per second. The feature is included in both the GLAD Advanced and GLAD Premium subscriptions. **How to enable it** Open a ticket at [i3D.net support](https://www.i3d.net/support/). *** ## 2026-10-15 — New `shutdown` command for FlexVM VMs `FlexVM` You can now shut down a FlexVM VM cleanly. Send `{"command": "shutdown"}` to `POST /v3/flexVM/clouds/{cloudUuid}/vms/{vmUuid}/commands`. FlexVM asks the guest OS to power off, so it can close its programs and write its data to disk first. If the VM is still running after 60 seconds, it is powered off at once. The `stop` command powers off the VM at once, like pulling the power cord. The guest OS gets no warning. Our documentation described `stop` as a graceful shutdown, which was not correct. Use `shutdown` when you want the guest OS to power off cleanly. See [Managing VMs](/compute/flexvm/managing-vms.md). *** ## 2026-10-12 — Dedicated Networks API: read access in beta `Dedicated Networks` The Dedicated Networks API is in beta. Any i3D.net client can now read networks, prefixes, IP addresses and fabrics, and check usage, with an existing API key. Creating, changing and deleting resources needs a contract amendment, so talk to your account manager to request one. Start with [Getting started](/connectivity/dedicated-networks-api/getting-started.md). The [API reference](/api/api_dedicated_networks.md) lists every operation, and each error code has its own page. *** ## 2026-08-11 — DDoS attack alerts now delivered to Microsoft Teams `Anti-DDoS` `GLAD` GLAD DDoS attack alerts can now be delivered to a Microsoft Teams channel, alongside the existing Slack and Discord options. Each alert names the attacked IP address, the size of the attack in Gbps, and the i3D location where the traffic is landing. **How to set it up** 1. In the Teams channel you want the alerts in, create a workflow using Microsoft's "When a Teams webhook request is received" trigger ([connector reference](https://learn.microsoft.com/en-us/connectors/teams/)). 2. Open a ticket at [i3D.net support](https://www.i3d.net/support/) and include the webhook URL. 3. Support registers the channel and walks you through the rest of the setup. Anyone holding that webhook URL can post into your Teams channel, so treat it like a password. *** ## 2026-05-19 — New Warden Edge in Sofia `GLAD Premium` Sofia is now live as a new Warden edge location. With Warden nodes distributed across i3D.net's highly-peered ASN, attack traffic is inspected and scrubbed as it enters the network from multiple points — spreading mitigation across entry points instead of concentrating it in a single place. This addition extends our coverage into Bulgaria as part of our ongoing worldwide capacity increase. All Warden users benefit automatically — no configuration needed. *** ## 2026-04-23 — Warden greylist PPS limits enforced per protected IP `Anti-DDoS` `GLAD Premium` Warden greylist PPS limits (`tcp-gl-pps` and `udp-gl-pps`) are enforced per individual protected (destination) IP address within your prefix, not shared across the prefix as a whole. A greylist PPS value of 50,000 on a /24 armor means each protected IP is independently limited to 50,000 PPS from greylisted sources — giving you a more granular and easier-to-understand control over unauthenticated traffic. There is no impact on performance or latency. *** ## 2026-04-20 — Warden IP List Improvements `GLAD Premium` During our maintenance window on April 20th we successfully migrated Warden to a new list storage backend. This brings two improvements for clients using the GLAD API. **Precise expiration times** Warden previously rounded `expires` values down to the nearest full clock hour — an entry set to expire at `19:55` was treated as `19:00` in the dataplane. This constraint is now removed. Expiration is applied with full precision, down to the minute. This makes short-lived, trust-based whitelisting practical: add an IP for a short window on a medium-confidence signal, then extend it when a stronger one follows — such as the IP entering an active game session. **Higher node availability** Warden nodes previously needed to stay offline for around a day after a software update. With the new backend, the time each node spends in maintenance is significantly shorter — so the reduced-capacity window is briefer. Each site runs multiple Warden nodes. A node going offline during an update reduces available scrubbing capacity at that location — it does not remove protection. No changes needed on your side. `POST /lists/{id}` works as before and existing entries are unaffected. *** ## 2026-04-03 — New Warden Edge in Dubai `GLAD Premium` Added Dubai as a new Warden edge location. With Warden nodes distributed across i3D.net's highly‑peered ASN, attack traffic is inspected and scrubbed as it enters the network from multiple locations — spreading mitigation across entry points instead of concentrating traffic in a single place. This addition extends coverage into the UAE as part of our ongoing worldwide capacity increase. No action required — the node is already active and all Warden users automatically benefit. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.i3d.net/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.