Valkey Release Notes

Last verified 10 Jul 2026

July 2026

15 July

  • Managed databases are available in Kansas City (mkc1) with limited plan availability. Premium AMD plans and General Purpose MongoDB clusters are not available in this region. See the regional availability matrix for current coverage by engine.

June 2026

30 June

  • DigitalOcean Managed Valkey database clusters now support custom CNAME records, allowing clients to connect through your own hostname instead of the default *.db.ondigitalocean.com address. Custom CNAMEs are available through the API when creating clusters or when updating an existing cluster, and apply to the public network connection only. For more information, see Configure Custom CNAMEs for Valkey.

April 2026

20 April

  • Managed databases support additional Premium AMD and Premium Intel plan options, which provide higher network throughput than Regular plans. For more information, see the create guides for PostgreSQL, MySQL, MongoDB, Valkey, OpenSearch, and Kafka.

15 April

  • Managed databases are available in Atlanta (atl1) and Richmond (ric1) with limited plan availability. Premium AMD plans are available in Atlanta only. See the regional availability matrix for current coverage by engine.

March 2026

10 March

  • Managed database clusters for PostgreSQL Standard Edition, MySQL Standard Edition, Valkey, OpenSearch, and Kafka now send email notifications when maintenance is scheduled, when it starts, and when it completes. See cluster notifications for PostgreSQL, MySQL, Valkey, OpenSearch, and Kafka for more information.

January 2026

8 January

  • The Network Access tab for managed databases now shows a resource type icon next to each trusted source, so you can distinguish sources that share the same display name, such as a Droplet and a tag. When you add trusted sources with Quick select, the dropdown also groups resources by type. To add trusted sources, see our guides for PostgreSQL, MySQL, MongoDB, Valkey, OpenSearch, and Kafka.

May 2025

16 May

7 May

  • You can now manually convert your Caching cluster to a Valkey cluster. All Caching clusters automatically convert to Valkey clusters by the Managed Caching discontinuation date.

April 2025

30 April

  • DigitalOcean Managed Caching is being discontinued on 30 June 2025.

    To replace Managed Caching, we are offering Managed Valkey, a Redis-compatible alternative with RDMA and higher throughput. All existing Managed Caching clusters automatically convert to Valkey clusters by 30 June 2025 during your upgrade window, retaining all data.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.