Live  /  DigitalOcean  /  Incident

DigitalOcean: Managed Database Clusters

DigitalOcean · digitalocean.comMinor incidentResolved2026-07-03 08:20 UTC
Public — what happened

Summary

DigitalOcean reported a minor issue starting at 22:04 UTC on July 2, 2026, in which customers could see slowdowns when creating, scaling, forking or restoring several kinds of managed database clusters, including Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka and Valkey, whether using the Cloud Control Panel or the API. The company said its engineers were still looking into the problem at 02:28 UTC and did not share a cause. DigitalOcean said a fix was put in place by 06:08 UTC, and it declared the issue resolved at 08:20 UTC on July 3.

Affected

Global, Global

As listed on DigitalOcean’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the DigitalOcean report →

More from DigitalOcean

The full archive is on the DigitalOcean status & history page.

Related: DigitalOcean status & history. SquidGrid is not affiliated with DigitalOcean.