# 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-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: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.i3d.net/changelog.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.