MySQL Release Notes

Validated on 5 Jun 2026 • Last edited on 28 Mar 2024

Upcoming Changes

• Managed MySQL 8.0 database clusters are scheduled for forced upgrades to MySQL 8.4 beginning 30 October 2026 during each cluster’s maintenance window.

  Learn more on MySQL 8.0 End of Life and Forced Upgrades Beginning 30 October 2026.

April 2026

28 April

• MySQL Advanced Edition clusters are now available in public preview, offering enhanced performance and scalability for production workloads.

September 2025

17 September

• Storage autoscaling is now in general availability. Additionally, you can now reduce your cluster’s amount of additional storage, as long as the new storage size is greater than or equal to the latest backup’s size plus any data growth since then and a 25% buffer.

• Now in public preview, you can now enable storage autoscaling on all Managed Database engines. To enable autoscaling, see our resizing guides for MySQL, PostgreSQL, MongoDB, OpenSearch, and Kafka.

July 2025

1 July

• The DOKS database operator, which facilitated integration of DOKS clusters with managed databases, is deprecated. Your existing databases remain operational and the operator-related CRDs are not removed. You can use the DigitalOcean API, CLI, or control panel to manage the databases created with the operator.

May 2025

16 May

• New managed database clusters are now automatically provisioned with default alert policies for CPU, memory, and disk utilization at a 90% threshold. These alerts notify you via email when resource usage is high, so you can investigate your application load or scale your cluster. You can modify or remove the default alerts at any time. For more information, see the following:

  • How to Set Up Kafka Cluster Monitoring Alerts
  • How to Set Up MongoDB Cluster Monitoring Alerts
  • How to Set Up MySQL Cluster Monitoring Alerts
  • How to Set Up OpenSearch Cluster Monitoring Alerts
  • How to Set Up PostgreSQL Cluster Monitoring Alerts
  • How to Set Up Valkey Cluster Monitoring Alerts

March 2025

19 March

• We have released new Storage-Optimized Droplet plans for MySQL and PostgreSQL with 48 CPUs, 384 GiB of RAM, and 20 TB (MySQL)/30 TB (PostgreSQL) of storage in SGP1, SFO2, and FRA1. For more details, see our pricing pages for MySQL and PostgreSQL.

February 2025

28 February

• All managed databases except MongoDB now support up to 2,000 IP addresses as trusted sources. To add trusted sources, see our guides for MySQL, PostgreSQL, Caching, MongoDB, OpenSearch, and Kafka.

December 2024

20 December

• All Managed Databases are now available in NYC2.

June 2024

17 June

• Managed databases now supports log forwarding to OpenSearch, Elasticsearch, and Rsyslog. You can create and manage log sinks using the control panel and DigitalOcean API. For more detailed steps, see our guides for MySQL, PostgreSQL, Redis, MongoDB, and Kafka.

April 2024

8 April

• You can now view hundreds of new database metrics by accessing the metrics API endpoint. For more detailed steps, see our guides for MySQL, PostgreSQL, Redis, and Kafka.

February 2024

13 February

• You can now reconfigure MySQL, PostgreSQL, and Redis databases via the API, which lets you edit many database engine parameters that were previously unavailable for editing. For more detailed steps, see How to Reconfigure Database Clusters.

September 2023

29 September

• The following MySQL and PostgreSQL plans are now deprecated:

  • MySQL and PostgreSQL plans with 8 vCPUs, 32 GB RAM, and 600 GB SSD ($480 per month)
  • MySQL and PostgreSQL plans with 16 vCPUs, 64 GB RAM, and 1,220 GB SSD ($960 per month)

  All of your existing database clusters with these plans are still functional and accessible to you. However, you cannot resize them. To regain access to these features, fork your database to a new cluster with a supported plan. For more detailed steps, see our guides on how to fork MySQL databases and fork PostgreSQL databases.

• When creating or resizing MySQL or PostgreSQL clusters on DigitalOcean, you can now add additional storage independently from your chosen database configuration plan. This provides a more economic option for increasing storage, rather than upgrading your cluster’s entire plan.

  For more details, see our guides on how to resize MySQL clusters and resize PostgreSQL clusters.

October 2022

13 October

• When creating a new Kubernetes cluster, you can add a free database operator (now in beta), which allows you to automatically link new databases to your cluster. For more details, see documentation on GitHub.

June 2022

27 June

• To improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.

March 2022

4 March

• You can now configure your MySQL, PostgreSQL, and Redis managed databases by making a PATCH request to /v2/databases/{database_cluster_uuid}/config. For example:

  {
    "config": {
      "sql_mode": "ANSI,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,STRICT_ALL_TABLES",
      "sql_require_primary_key": true
    }
  }

  For more details, see the full reference documentation for the managed databases API.

February 2022

1 February

• The database online migration feature for the MySQL, PostgreSQL, and Redis database engines no longer supports migrating databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean.

January 2022

25 January

• Online migration is now available for the MySQL, PostgreSQL, and Redis database engines. Online migration allows you to migrate databases from external servers or cloud providers to databases in your DigitalOcean account.

6 January

• All DigitalOcean databases now support App Platform apps as trusted sources, including MongoDB.

August 2021

9 August

• Released v1.63.0 of doctl, the official DigitalOcean CLI. This release includes a number of new features:

  • The database firewall sub-commands now support apps as trusted sources
  • New monitoring alert sub-commands for creating and managing alert policies
  • The --droplet-agent flag was added to the compute droplet create sub-command to optionally disable installing the agent for the Droplet web console

March 2021

30 March

• You can now deploy managed databases on Droplets with dedicated CPUs for the PostgreSQL, MySQL, and Redis engines.

June 2020

16 June

• You can now remove all global SQL modes from MySQL database clusters. Global SQL modes affect the SQL syntax MySQL supports and the data validation checks it performs.

5 June

• Beginning 4 June 2020, you are required to create a primary key for each new table in any DigitalOcean Managed MySQL Database to improve cluster performance.

April 2020

28 April

• The DigitalOcean Virtual Private Cloud (VPC) service is now available for all customers. VPC replaces the private networking service. Existing private networks will continue to function as normal but with the enhanced security and features of the VPC service. See the description of VPC features for more information.

7 April

• We began the incremental release of the DigitalOcean Virtual Private Cloud (VPC) service. It will be available for all customers soon. VPC replaces the private networking service.

March 2020

4 March

• Users can now set legacy MySQL 5x password encryption for MySQL 8+ managed databases from the control panel and API.

January 2020

27 January

• v1.13.0 of the DigitalOcean Terraform Provider is now available. This release adds support for tagging managed databases clusters.

December 2019

19 December

• Released v1.12.0 of the DigitalOcean Terraform Provider. This release contains improvements to Managed Database support including a new resource for configuring trusted sources and the ability to set the global SQL mode or Redis eviction policy on a cluster. There is also a new data source for finding supported Kubernetes versions. Learn more on the Terraform Changelog.

17 December

• Bandwidth billing for managed databases, originally slated to begin in January 2020, has been postponed to 2021. Egress bandwidth for managed databases clusters will continue to be waived until then.

November 2019

21 November

• Users can now use the DigitalOcean API to set and modify trusted sources for managed databases to restrict incoming connections.

• MySQL managed database clusters now support setting the global SQL mode via the control panel and the API. See How to Set Global SQL Mode on MySQL Clusters for more information.

September 2019

4 September

• Managed databases for MySQL and Redis are now available in SGP1, BLR1, and TOR1, and MySQL is now in General Availability. Learn more in the MySQL and Redis announcement blog post.

August 2019

27 August

• Managed databases for MySQL and Redis in Limited Availability are now available in the AMS3, LON1, and NYC3 datacenter regions. Learn more in the MySQL and Redis announcement blog post.

20 August

• Managed databases for MySQL and Redis have been released in early availability in the NYC1, FRA1, and SFO2 datacenter regions. Learn more in the MySQL and Redis announcement blog post.