Live  /  DigitalOcean  /  Incident

DigitalOcean: Managed Databases Creation

DigitalOcean · digitalocean.comMinor incidentResolved2026-08-23 14:33 UTC
Public — what happened

Summary

DigitalOcean said that starting at 05:11 UTC on August 23, 2026, users could run into errors when trying to set up new Managed Database clusters, whether through its web control panel or its API. The company later described the problem as spanning multiple regions and said it was working on a mitigation, without naming a cause. By 11:30 UTC it reported fixes in place for the NYC3 and NYC1 regions and began watching for stability. DigitalOcean marked the issue resolved at 14:33 UTC, saying cluster creation was working normally again.

Affected

NYC1, NYC3

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.